delete_checklists

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

With no annotations, the description carries the full behavioral burden, but it only states the action and the return value. It does not disclose that deletion is permanent, whether it cascades to associated tasks or templates, any permission requirements, or error behavior.

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 short and front-loaded, with the core action stated in one sentence and then minimal, clear Args and Returns sections. Every line earns its place and there is no filler.

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 simple one-parameter call, the description and existing output schema are mostly sufficient. However, for a destructive bulk operation with no annotations, the missing permanence/cascade caveats are a notable gap that an agent would benefit from before invoking it.

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%, but the description explicitly defines checklist_ids as 'List of checklist IDs to delete,' adding meaning beyond the bare schema type and title. It fully conveys the single parameter's purpose, though details like empty-list validity or existence requirements are not addressed.

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 opening sentence 'Delete multiple checklists' names a specific verb and resource, and 'multiple' plus the 'checklist_ids' parameter make the bulk nature clear. This distinguishes it from sibling tools like update_checklist, complete_checklist, or get_checklist.

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 given on when to use this tool rather than alternatives, no prerequisites are mentioned, and there is no stated exclusion for single or task-level deletions. The description provides no routing information relative to the many sibling checklist tools.

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