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

Annotations already declare readOnlyHint=false, destructiveHint=false and idempotentHint=false, so the safety bar is low, yet the description still adds real context: it copies facts (title, link, place, type), starts the note empty rather than inheriting the curator's, records provenance, and explicitly leaves the source list and save untouched. It never mentions retry/idempotency_key handling despite idempotentHint=false, which is the remaining gap.

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 tight sentences, front-loaded with the action and target before the behavioral detail. The aside about the curator's words is slightly literary but still earns its place by explaining why the note is empty.

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 3-parameter, no-output-schema mutation tool with full annotation coverage, the description covers side effects, provenance and the copied field set. It does not state what the call returns or how failures/retries behave, which is a minor omission.

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 100% and every parameter (list, itemId, idempotency_key) is already documented in the schema, so the baseline is 3. The description adds only a mild constraint ('one of your own lists') and no format or syntax detail for the itemId beyond what the schema states.

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 ('Add') and resource ('a pick ... to one of your own lists as a new pick'), and names the origin set ('usually one from saved_items'), which separates it from a generic add_item. It does not name the sibling it competes with (add_item/save_item), so it falls short of 5.

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?

'usually one from saved_items' implies the intended use case, but there is no explicit when-to-use versus add_item or save_item, and no stated exclusions or prerequisites. Usage is inferable rather than spelled out.

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