Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description bears the full burden of behavioral disclosure. It only states the core mutation ('Create'), but does not mention side effects, persistence behavior, required permissions, validation failures, or what happens on success. This is minimal disclosure for a write operation.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is extremely concise, with no filler or redundant clauses. However, it is so sparse that it nearly restates the tool name, making it under-specification rather than effective concise communication.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple flat create operation with an output schema present, the basic purpose is covered. But with no annotations and no usage or behavioral context, important details like tag optionality, response shape, and side effects are left entirely to inference or the schema, leaving clear gaps.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, and the description does not mention title, content, or tags at all. The schema provides the raw property names, types, and required/default information, but the description adds no semantic meaning and fails to compensate for the lack of parameter docs.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states a specific action ('Create') and resource ('a new note'), which distinguishes it from the read/search/delete sibling tools. It lacks any additional scope or detail about what a note consists of, but the core purpose is unambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description gives no guidance on when to use this tool versus alternatives, no context about prerequisites, and no exclusions. The verb 'create' implies use for new notes, but the description fails to explicitly say when search_notes or read_note would be more appropriate.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description carries the burden of disclosing behavioral traits. It labels the action as 'Delete' but does not mention permanence, irreversibility, permission requirements, side effects, or what happens when the note does not exist. For a destructive operation, this is a notable gap.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, concise sentence with no redundant words. It is front-loaded with the action and resource, making it immediately scannable.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple one-parameter delete operation with an output schema, the description is minimally adequate. It clearly names the resource and the required identifier. However, without annotations it could be more complete by noting the destructive/irreversibility implication or error behavior.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema has 0% description coverage for the single parameter note_id. The description's 'by ID' adds little beyond the parameter name itself, which already indicates that note_id is the identifier. No additional details about format, source, or constraints are provided.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific action ('Delete') and resource ('a note') with a clear identifier scope ('by ID'). It is immediately distinguishable from sibling tools like create_note, search_notes, and read_note, all of which imply different operations.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance is given on when to use this tool versus alternatives, nor are prerequisites, caveats, or exclusion criteria mentioned. The description simply states the operation without contextual direction.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description carries the burden of behavior disclosure. It clearly indicates a read-only operation and references ctx.read_resource(), but it does not describe error handling, not-found behavior, or whether any side effects occur.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is short and front-loaded with the essential action. However, the second sentence 'Demonstrates ctx.read_resource()' is meta-context that does not help an agent select or invoke the tool correctly, so not every sentence earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple single-parameter read tool with an output schema, the description is minimally adequate. It is missing guidance on when to use this tool versus search_notes and what happens when the note_id does not exist, leaving notable gaps for an agent operating without richer context.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must compensate. 'By ID' adds meaning by mapping note_id to the note identifier, but it provides no additional detail about the ID format or where it comes from beyond the property name.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the verb 'Read' and the resource 'a note by ID', which is specific enough for an agent to understand the core operation. It is naturally distinct from the sibling tools create_note, search_notes, and delete_note, though it does not explicitly name these alternatives.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Does the description explain when to use this tool, when not to, or what alternatives exist?

The phrase 'Read a note by ID' implies this tool should be used when the agent already has a note_id and wants the note's content. However, it does not explicitly say when to prefer this over search_notes or what to do when the ID is unknown.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries the behavioral burden. It adds value by specifying that matching occurs in title or content and 'search' implies a read-only operation, but it does not disclose matching semantics, case sensitivity, pagination, or whether results are summaries or full notes.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is one efficient sentence with no filler. It front-loads the verb and resource and immediately states the search scope, making it easy to parse quickly.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a single-parameter search tool, the description provides sufficient core context, and the presence of an output schema covers the return shape. Minor gaps remain around exact vs. partial matching and ordering or limits, but these are not critical for basic use.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema only provides a bare 'query' string with no description, so the description must compensate. It defines query as a keyword and identifies the fields being searched, which adds meaning, but it leaves match-mode details and result-limit behavior undocumented.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses a specific verb ('Search'), names the resource ('notes'), and defines the search scope ('keyword in title or content'). It clearly differentiates from the sibling CRUD tools (create_note, read_note, delete_note) by indicating a lookup operation.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Does the description explain when to use this tool, when not to, or what alternatives exist?

The intended use case is clear: call this tool when you need to find notes by keyword. The sibling names make the distinction obvious, and no other search alternative exists, though the description does not explicitly state when not to use this tool.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.