remove_note

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

Fully discloses behavioral traits without annotations: soft deletion, reversibility, and derived entity consequence. No contradictions.

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?

Three sentences plus parameter detail, tightly packed with essential info. No fluff.

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?

Adequately covers purpose, side effects, and user guidance. Could mention return value, but tool is simple and well-integrated with sibling restore_note.

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 has no parameter descriptions (0% coverage). Description clearly defines 'note' as the Id to remove with an example, fully compensating for schema gap.

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?

Clearly states 'Remove a note' with specific verb and resource. Differentiates from sibling restore_note by emphasizing soft deletion and reversibility.

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?

Provides usage context: soft deletion with recovery via restore_note, and mentions entity disappearance. Could be more explicit about when not to use, but siblings include only restore_note, making it clear.

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