delete_note

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

Description only says 'delete' without elaborating on side effects (e.g., permanent removal, return value, permission requirements). With no annotations, the description should provide more behavioral context but is minimal.

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?

Single, direct sentence with no wasted words. Front-loaded with the action and resource, followed by parameter method. Efficient and to the point.

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 delete tool with one parameter and no output schema, the description is sufficient. It explains what the tool does and the required input. Could mention whether deletion is permanent or confirmable, but not necessary for basic understanding.

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 covers the single parameter 'id' with description 'Note ID to delete'. The description adds 'numeric' which aligns with integer type. Schema description coverage is 100%, so baseline is 3; description adds minimal extra 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?

Description clearly states the action (delete) and resource (note) with the method (by numeric ID). It distinguishes from sibling tools add_note and list_notes, which serve different purposes.

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?

Description implies usage when a specific note needs to be deleted, but does not explicitly state when not to use it or mention alternatives. No exclusions or context for when this tool is appropriate over others.

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