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

No annotations are supplied, so the description carries the full behavioral burden and does so: it declares the operation DESTRUCTIVE, discloses the phase cascade (child tasks also deleted), states the confirm gate blocks all deletion, names the API-key auth requirement, and says data goes to the project trash and is restorable for 30 days.

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?

Three dense sentences, front-loaded with the irreversible action and the cascade scope, then the safety protocol, then the recovery path. Every clause carries information an agent needs; nothing is padding.

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 two-parameter destructive tool with no annotations and no output schema, the description covers everything material: auth, cascade effects, the confirmation gate, and recoverability. An agent has no remaining question that would change how it calls this tool.

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 both taskId and confirm are already documented, and the description largely restates the confirm contract ("pass confirm: true only after they agreed") rather than adding new parameter meaning. The cascade note implicitly raises the stakes of taskId but adds no syntax or format detail beyond the schema.

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?

Uses a specific verb and resource ("Delete one task") and immediately scopes it: one task in the connected LoopGantt account, cascading to every task under it when the target is a phase. That cascade clause plus the account qualifier distinguishes it cleanly from siblings like update_task and complete_task.

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?

Explicit precondition for calling: ask the user first and pass confirm: true only after agreement, with "without it nothing is deleted" spelling out the consequence of skipping it. It does not name sibling alternatives (e.g. use complete_task to mark done instead), so it falls short of full when/when-not routing.

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