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

With no annotations, the description carries the behavioral transparency burden. It states the core mutating behavior (create), but it does not disclose whether the operation is idempotent, requires any permissions, or how existing notes might be affected. The described behavior is minimal beyond the basic create action.

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, starts with the primary purpose, and then lists parameters with concise explanations. Every sentence contributes information, no filler or repetition, making it appropriately sized and front-loaded.

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 creation tool, the description is nearly complete: it states the action and defines both parameters. With an output schema present, return value explanation is unnecessary. Minor gaps like storage behavior or prerequisites do not seem blocked for this basic tool.

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, so the description's argument explanations are essential. It adds meaning by defining title as a short name with an example ('Groceries') and content as the body text, which a schema that only lists string types does not convey. This is useful contextual meaning.

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 'Create a new note' states a specific verb (create) and resource (note) with the qualifier 'new', making it clear this tool adds a note rather than modifies or retrieves one. This clearly distinguishes it from sibling tools like update_note, read_note, and delete_note.

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 implies usage when a new note is needed but provides no explicit when-to-use/alternatives guidance. There is no mention of when to prefer this over update_note or other siblings, leaving inference to the agent.

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, the description carries the full behavioral disclosure burden. It does state that deletion is permanent, which is a crucial destructive trait, but it does not address error behavior, idempotency, permissions, or what happens when the title does not exist. This is a minimal but not rich disclosure.

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 clear sentence with a brief Args section. It is front-loaded with the core behavior and contains no filler or redundant information.

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 destructive tool, the description covers the essential information: the action, the permanence, and the identifying parameter. An output schema exists, so return values need not be explained. Minor gaps like error behavior remain, but they are not critical for a simple delete operation.

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. It defines 'title' as 'The title of the note to delete,' which clarifies that the title is the identifier for the note to be removed. However, this largely restates the parameter name and adds no nuance about matching, case sensitivity, or uniqueness.

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?

States a specific verb ('Delete') and resource ('note') with the key qualifier 'permanently,' which clearly distinguishes it from sibling tools like read_note, update_note, and search_notes. The intent is immediately obvious and 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?

No guidance is given about when to use this tool versus alternatives, nor are any exclusions or prerequisites mentioned. The only implicit signal is the tool name and the verb 'delete,' which does not constitute explicit usage guidance.

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, the description carries the full behavioral burden. It usefully discloses that the tool returns only titles, not full note content, and that it covers all saved notes. However, it omits any detail about ordering, pagination, or access/read-only semantics.

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?

A single, front-loaded sentence with no filler. Every word contributes meaning and the description is 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 zero-parameter listing tool with an output schema available, the description adequately conveys what the tool returns. The main missing element is explicit routing to sibling tools, but the low complexity makes this a minor gap.

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 tool has zero parameters and the schema is empty with 100% coverage, so the baseline of 4 applies. No additional parameter explanation is needed.

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, 'List', and a specific resource, 'titles of all saved notes'. It clearly distinguishes itself from single-item operations like read_note and mutations like add_note/delete_note through the 'all saved notes' scope, though it does not explicitly name or contrast those siblings.

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 provided on when to use this tool versus alternatives. It does not mention search_notes for targeted retrieval or read_note for full content, leaving the selection logic entirely to inference.

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 full burden of behavioral disclosure. It states the core read behavior but does not mention behavior on missing titles, error handling, or whether any uniqueness or exact-match constraints apply. The description adds minimal context beyond the tool name.

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 concise, front-loaded with the purpose, and includes only the necessary parameter explanation. Every part 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?

Given the simple one-parameter signature and the presence of an output schema, the description is nearly complete for calling the tool. It could mention what to do when the title does not exist or how to discover valid titles, but those are not required to invoke the tool correctly.

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 description explicitly defines the single parameter, saying 'title: The title of the note to read.' This adds a little meaning beyond the schema, which only says the property is a string named 'title.' It does not add constraints, exact-match expectations, or format details, but for one simple string parameter that is adequate.

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 action ('Read') and the resource ('one note'), and 'full content' distinguishes it from list/search operations. It does not explicitly name sibling tools, but the verb-resource-scope combination makes the purpose clear.

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 does not say when to use this tool versus alternatives such as list_notes or search_notes. It only describes the operation itself; any usage context such as 'when you already know the note's title' is implied rather than stated.

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, the description carries the full burden of behavioral disclosure. It discloses that the search is case-insensitive and matches title or content, which is valuable. It does not explicitly state it is a read-only operation (though 'Find' implies this), nor does it mention result ordering, pagination, or limits. The description is adequate but not rich.

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 two compact sentences plus a one-line argument definition. It front-loads the main purpose and includes the case-insensitivity detail early. No fluff or redundancy; 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 search tool with one parameter and an output schema present, the description covers the essential context: what is searched and how (case-insensitively). It does not mention result limits or error behavior, but the output schema likely handles return format. With no annotations, some behavior context is missing, but it is reasonably complete for the tool's simplicity.

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. It does: 'query: The text to search for.' clearly explains the meaning and usage of the only parameter, adding value beyond the bare schema which only provides the type. It could elaborate on formatting or examples, but for a single string parameter this is sufficient.

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 verb ('Find') and resource ('notes'), and specifies that it searches both title and content for a query. This clearly differentiates it from siblings like list_notes (which lists all), read_note (which fetches a single note), and add/update/delete (which are mutations).

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 implies usage: use this when you need to locate notes by text content/title rather than listing all notes. However, it does not explicitly name sibling tools or state when not to use it (e.g., 'for listing all notes, use list_notes'). The purpose is clear enough that an agent can infer the intent, but no explicit routing is given.

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, the description carries the full behavioral burden. It explicitly discloses that content 'overwrites the old content', which is critical destructive behavior. It does not mention error behavior for nonexistent notes, permission requirements, or idempotency, but the overwrite warning is meaningful and prevents an agent from assuming additive behavior.

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: the first sentence states the purpose, and the Args list is a compact structured format for parameters. Every sentence contributes value, with no redundancy or filler.

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 update tool, the description covers the core behavior and both parameters. It does not discuss the case where the title does not exist or what the output contains, but an output schema exists and the overall context is small. A minor gap is the lack of explicit error or idempotency details, which prevents a perfect score.

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. It does: 'title' is clearly the note identifier, and 'content' is the replacement body text with overwrite semantics. These descriptions go beyond the schema's raw 'string' type, giving an agent enough meaning to supply correct values.

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 ('Replace') and resource ('existing note'), which clearly differentiates it from siblings like add_note, read_note, or delete_note. The verb 'replace' unambiguously indicates an update operation, so an agent can tell what this tool does without inspecting the schema.

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 'existing note' implies this tool is used for modifying notes that already exist, and the overwrite semantics hint that it is not for creating new notes. However, it does not explicitly name alternatives, state when not to use it, or call out add_note for creating notes. The usage guidance is implied rather than explicit.

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