delete-todo-checklist-item

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so irreversibility is covered structurally. The description reinforces 'This cannot be undone', which is good corroborating context. But it doesn't mention the optional confirm gate (which the schema describes) or that missing confirmation returns an error without touching data — that behavioral nuance lives only in the schema.

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?

Very tight: one sentence plus one clearly-marked TIP. Front-loaded with the action and the key constraint (irreversible). No waste.

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 destructive mutation with rich annotations and 100% schema coverage, the description covers what and why, plus ID provenance. Minor gap: no mention of the confirm-gate behavior, which is important for correct invocation when enabled, though the schema supplies 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 100%, so the schema fully documents all 7 params. The description adds the dependency direction ('Requires checklistItemId from list-todo-checklist-items'), which is useful chaining info beyond raw schema. Baseline is 3; the ID-sourcing hint nudges it to 4.

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+resource ('Delete a checklistItem object') and the tip clarifies it removes a step from a To Do task. Clear, though it doesn't explicitly distinguish itself from sibling delete-todo-task or other deletion tools beyond the resource name.

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 TIP explains the domain context (a step of a To Do task) and points to the source of the required ID ('Requires checklistItemId from list-todo-checklist-items'). That is useful routing. However, there's no explicit when-to-use vs. when-not-to-use, and no mention of the confirm gate or prerequisite creation flow.

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