Edit item

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

The annotations already indicate this is a mutating, non-idempotent operation, and the description's 'Edit' aligns rather than contradicts that. It adds that move, tags, dates, and status can be changed, but it does not disclose side effects, persistence, or caveats about replacing versus merging values.

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?

The single-sentence description is tight and front-loads the core action and resource. It wastes no words, though brevity comes at the cost of important operational detail.

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 tool with 25 parameters and only 16% schema coverage, a one-line overview is not enough to invoke correctly. Key details about how the target is identified, how optional move/tag/date changes are expressed, and the behavior of clear/replace flags are missing.

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 description coverage is only 16%, so the description would need to compensate for 25 parameters, but it only loosely groups fields as 'move, tags, dates, and status.' It does not explain identity selection, clearing fields, moving destinations, tag handling, or date formats.

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?

The description clearly identifies the action ('Edit'), the resource ('a task or project'), and the main areas: move, tags, dates, and status. It does not explicitly differentiate from sibling tools like move_items or complete_items, so it is clear but not strongly distinguished.

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?

There is no guidance on when to use edit_item versus siblings such as move_items, set_repetition, append_note, or complete_items. The description implies broad editing but never states exclusions or narrower alternatives.

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