delete_entity_checklist

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

Annotations already declare destructiveHint=true, so the safety profile is covered. The description adds only the scope (all items, project/portfolio), and omits useful behavioral context such as whether the operations are irreversible, why 'confirm' is required, or what 'notify' triggers.

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 zero filler, which is appropriately tight for a scoped delete. It is arguably too terse given the destructive bulk nature, but it wastes no words.

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 bulk operation with no output schema and only 50% schema coverage, the description should explain the confirm-gate, reversibility, and notify semantics. None of that is present, leaving the agent to infer the consequences of an irreversible bulk delete.

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 50%; 'confirm' and 'entityType' are documented in the schema, but 'notify' and 'entityId' have no descriptions anywhere. The description adds no parameter meaning beyond restating the project/portfolio scope already present in the entityType enum description.

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) plus resource and scope (all checklist items on a project/portfolio), which distinguishes it from the item-level siblings delete_entity_checklist_item and delete_checklist_item. However, it never names those alternatives explicitly, so differentiation relies on the agent inferring 'all' means bulk entity-level.

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 word 'all' implies this is the bulk variant versus the single-item deletion siblings, giving implied usage context. There is no explicit when-to-use/when-not statement, no mention of prerequisites, and no routing to alternatives for single-item deletion.

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