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

Beyond the readOnly/idempotent annotations it usefully discloses the response-envelope + nextAction pattern and the polling field (pollStartedAt), which an agent needs to chain calls. However the "confirm: false … then confirm: true" instruction describes a two-step commit flow with no readOnly equivalent and references a parameter that does not exist in the schema, which is confusing for a tool annotated as a pure read.

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 the core action and four short, information-dense sentences with no filler. The inline operation enum duplicates the schema's enum and could be dropped without loss.

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?

With 12 parameters, an output schema and full annotations, most structured burden is already carried, and the description covers the detail flag and the nextAction loop. But it omits ID selection behavior across the multiple per-type IDs and references a nonexistent confirm flag, leaving the agent to reconcile the description against the schema.

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 the baseline is 3; the description adds real value only for detail=true and the nextAction/polling handshake. It also introduces a `confirm` parameter absent from the schema, which actively misleads rather than clarifies.

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?

"Read one saved item" is a specific verb+resource and the appended operation list makes the breadth of item types explicit, which separates it from list_items. It never names update_item or list_items, so the boundary with siblings is implied rather than stated.

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?

It gives concrete usage conditions: set detail=true before editing, use confirm:false for preview then repeat with confirm:true, and follow the primary nextAction from the envelope. It stops short of saying when to prefer list_items (multiple items) or update_item (to make the edit), which would complete the routing.

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