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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the bar is lower, and the description still adds high-value specifics: the cascade scope (associated test cases, scripts, and executions are also destroyed) and the ownership requirement. It stops short of stating that the deletion is irreversible or whether any confirmation/soft-delete exists.

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 short sentences, front-loaded with the action, then the precondition, then the blast radius. Every sentence earns its place with zero filler.

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 full schema coverage and no output schema, the essentials are present: what it deletes, what else gets deleted, and who may call it. Only the permanence/recovery question is left unaddressed.

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 100%, with project_id documented and the context parameter given a detailed usage contract, so the schema carries the burden. The description adds no parameter-level meaning beyond what is already structured. Baseline 3 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 cleanly separates it from delete_test_case, delete_script, and delete_deploy_integration among the siblings. It does not explicitly name an alternative or say how it differs from update_project, but the resource is unambiguous.

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?

"Requires ownership" is a real precondition that shapes whether an agent may call it at all. However, there is no guidance on when to prefer this over alternatives (e.g., archiving, or deleting individual test cases/scripts instead) and no explicit when-not-to-use warning.

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