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

With no annotations at all, the description carries the full burden and discloses almost nothing: it doesn't say whether unpinning is idempotent, whether it errors when the note isn't pinned, whether the note content is untouched (important, since delete_note is a sibling and agents may conflate the two), or what permissions are needed.

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 short sentence, front-loaded with the action and free of filler. It is efficient but borders on under-specification given the mutation semantics.

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 mutation tool with zero annotations, no output schema, and a required parameter undocumented in both schema and description, the definition leaves too much for the agent to infer about side effects and failure modes.

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 coverage is only 50%: the required 'id' parameter has no description anywhere, and the description adds no clarification about what id refers to (note id vs. pin id) or its format. The one documented parameter, 'workspace', is explained entirely in the schema, so the description contributes nothing.

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 and resource ('Unpin a note') plus where the pin lives ('Caddie's sidebar'), which is clearer than the bare name. It doesn't explicitly contrast with the inverse sibling pin_note or with delete_note, but the verb itself 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?

No guidance on when to unpin versus pin_note, delete_note, or move_note, and no stated preconditions (e.g., that the note must currently be pinned). The only routing hint lives in the schema's workspace description, not the tool description.

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