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

Annotations already declare destructiveHint=true and idempotentHint=true, so the risk profile is partly covered. The description adds a genuinely non-obvious behavioral rule: the curator note is the curator's own words and is never rewritten by AI, which an agent must respect when editing. It does not restate clearing semantics or note that omitted fields are left unchanged.

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?

Front-loaded with verb, scope and editable fields in one sentence, followed by a short behavioral caution. No filler, though 'so preserve their voice' mildly restates 'never rewritten by AI'.

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?

No output schema, so return values need not be described; annotations cover the safety profile. The description covers the field set and the key note-preservation rule, but omits permission/ownership requirements and whether unspecified fields are preserved.

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%, so every parameter is already documented, including empty-string clearing for url, note and author. The description lists the same four editable fields without adding format, precedence or interaction details beyond the schema. Baseline 3 applies when the schema carries the parameter burden.

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?

Names a specific verb (Edit) and resource (one pick) and enumerates the editable fields (title, note, URL, author), which cleanly separates it from sibling list-level tools like update_list or membership tools like move_items. It stops short of naming an alternative or stating scope conditions, so it is clear but not fully differentiated.

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?

Usage is only implied: editing metadata on an existing pick vs. add_item for new picks, remove_item or archive_list for removal. No explicit when-to-use or when-not-to-use conditions are given. The one constraint it does state (preserve the curator's voice in the note) is a real usage rule but not alternative-routing guidance.

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