Delete Tracker project

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

Annotations already declare destructiveHint=true, readOnlyHint=false, and idempotentHint=false, so the safety profile is covered. The description reinforces this with '(irreversible)' and adds one genuinely new fact — that the call returns an acknowledgement — which matters since there is no output schema. It stops short of explaining side effects on dependent data.

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?

Two short sentences, front-loaded with the destructive action and its irreversibility. No filler, no restatement of the parameter.

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 single-parameter destructive operation with full annotation coverage and no output schema, the description supplies the essentials: what is deleted, that it cannot be undone, and that the response is an acknowledgement. Missing only secondary detail like permission requirements or effects on related issues.

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%: the single parameter project_id is documented as the numeric id sourced from projects_list. The description adds nothing beyond that, so the baseline 3 for full schema coverage applies.

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 and resource ('Delete a project'), which is unambiguous and matches the tool name. It does not explicitly differentiate itself from other delete siblings (e.g. tracker_boards_delete, tracker_sprints_delete), but the resource noun makes the target clear enough for an agent.

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?

There is no guidance on when to use this tool versus alternatives, no prerequisites (e.g. permissions, ownership), and no warning about cascading effects on child entities. The only usage signal is the parenthetical '(irreversible)', which is a caution, not selection guidance.

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