delete_list_item

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

The annotations already declare destructiveHint=true and idempotentHint=true, and the description reinforces this with 'permanently removes the item,' which is the key irreversible consequence an agent must weigh. It adds the redirect to a non-destructive alternative, but says nothing about error behavior for missing/unknown IDs or whether any cascade occurs.

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 purpose, then usage scenarios, then the destructive caveat — good ordering and no filler. The parameter list largely duplicates the schema and could be dropped to tighten it further.

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 two-parameter delete with no output schema, the description covers the essential decision (permanent removal vs. status update). Minor gaps: no mention of what happens on invalid IDs or whether child data is affected.

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 both parameters are already documented with identical wording in the schema, so the description's parameter block adds no syntax or constraint information. Baseline 3 applies when the schema carries the full load.

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 and resource ('Remove an item from a list') and the parameter names make the scope unambiguous, so an agent can distinguish it from delete_list and delete_calendar_event at a glance.

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?

Explicit 'Use this when' bullets give concrete scenarios (added by mistake, deleting rather than completing), and it names the alternative — update_list_item with status="completed" — for the check-off case. When-to-use and when-to-use-something-else are both covered.

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