delete_entity_checklist_item

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the safety profile is covered. The description adds only the project/portfolio scoping; it says nothing about the confirmation requirement, the notify behavior, or irreversibility beyond what the annotation implies.

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?

A single front-loaded sentence with no wasted words. It is efficient, though its brevity contributes to the gaps noted in other dimensions rather than being an independent virtue.

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?

A destructive, confirmation-gated tool with five parameters and no output schema needs more than one sentence. The description omits the confirm requirement, the notify behavior, and any return/error information, leaving the agent to infer invocation behavior entirely from the schema.

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 only 40% (confirm and entityType are documented in-schema; itemId, entityId, notify are not). With low coverage the description should compensate, but it adds no semantics for any of the five parameters, including the notify flag.

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 (Delete), resource (checklist item), and scope (of a project/portfolio), which distinguishes it from the issue-level delete_checklist_item sibling. It is clear but does not explicitly name the alternative tool an agent might confuse it with.

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 when-to-use guidance, no prerequisites, and no conditions under which this tool should be chosen over delete_entity_checklist, update_entity_checklist_item, or delete_checklist_item. The entity-type hint is the only routing signal.

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