Delete Todos (Bulk)

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

Annotations already indicate destructiveHint=true, readOnlyHint=false, and idempotentHint=false. The description adds valuable context beyond this: it specifies the safety limit (default limit=10) and the requirement for at least one filter, which are not covered by annotations. It does not contradict annotations, as 'Delete' aligns with destructiveHint=true.

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 a single, efficient sentence that front-loads the core action and key constraints (filters, safety limit). Every word serves a purpose with no redundancy, making it highly concise and well-structured.

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?

Given the tool's complexity (destructive bulk operation with 8 parameters), annotations cover safety aspects, and an output schema exists, the description is mostly complete. It adds important behavioral context (filter requirement, safety limit) but could benefit from more explicit guidance on alternatives or error handling, though the output schema reduces the need for return value explanation.

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 100%, so the schema fully documents all 8 parameters. The description adds minimal semantics by mentioning the safety limit and filter requirement, but does not provide additional meaning beyond what the schema already covers. Baseline is 3 due to high schema coverage.

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 ('Delete multiple todos') and scope ('matching filters'), distinguishing it from the sibling 'delete_todo' which likely deletes a single todo. It specifies bulk deletion with filtering, making the purpose specific and 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?

The description provides clear context for when to use it ('requires at least one filter') and mentions a safety default ('defaults to limit=10 for safety'), but does not explicitly state when to use this vs. alternatives like 'delete_todo' or other sibling tools. It implies usage through filtering but lacks explicit alternatives.

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