remove_item

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

With no annotations, the description carries the full burden. It states the action but doesn't disclose whether removal is permanent, what happens to subtasks, what occurs if both id and name are provided, or error behavior when the item isn't found. The phrase 'Provide either id or name' is parameter guidance, not behavioral disclosure.

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 description is two short sentences, front-loaded with the purpose, and contains zero redundant or irrelevant information. Every word earns its place.

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?

The tool is simple and an output schema exists, so return values don't need to be explained. However, the description lacks differentiation from 'batch_remove_items' and doesn't cover important behavioral details like the required item_type or the mutual exclusivity of id/name. It's adequate for a basic understanding but has clear gaps.

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 0% and parameters lack descriptions. The description adds meaning by indicating that id and name are alternative identifiers ('Provide either id or name') and that item_type relates to 'task or project'. This clarifies all three parameters beyond what the schema provides, though it doesn't explicitly state enum values or the requirement to provide at least one identifier.

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 states the action ('Remove') and the resource ('a task or project from OmniFocus'), which is specific and unambiguous. It distinguishes from the sibling 'batch_remove_items' by implying single-item removal, even though it doesn't explicitly say so.

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 is provided on when to use this tool versus alternatives like 'batch_remove_items'. The description doesn't mention exclusions, prerequisites, or scenarios where another tool would be more appropriate.

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