bear_trash_note

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

Adds context beyond annotations by clarifying it's a soft delete (recoverable) and that the note is identified by its ID. Annotations only indicate destructive=true, but description specifies recoverability.

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?

Extremely concise (20 words, 2 sentences) with front-loaded action and key behavioral detail. No unnecessary words.

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 tool with one parameter and no output schema, the description fully covers purpose, behavior, and identification. No gaps given complexity.

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 100% of parameters with description. The description adds minimal additional meaning beyond confirming the ID's role.

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 (move to trash), the resource (Bear note), and distinguishes it from siblings like 'bear_archive_note' by specifying it's a soft delete with recovery option.

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?

Implies usage for soft deletion with recovery, but does not explicitly state when not to use or compare with alternatives like archiving or permanent deletion.

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