Delete Project

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

Annotations already declare destructiveHint=true and readOnlyHint=false. The description adds 'permanently and irreversibly' (reinforcing destructive) and 'subject to existing Container guards' (new context). However, it does not disclose whether deletion cascades to associated tasks/notes or what happens if guards block deletion, leaving key behavioral details vague.

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?

The description is one tightly-worded sentence that includes a warning and key constraints. Every word earns its place, with no fluff or redundancy.

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?

The tool is simple (one parameter) but destructive and irreversible. The description covers permanent deletion, confirmation requirement, and container guards, but does not clarify what 'Container guards' are or explain consequences for dependent data. Given the high-stakes nature, more context would be expected for full completeness.

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 0%, and the description does not mention project_id or add any meaning beyond the parameter name. The single parameter is self-explanatory, but the description fails to compensate for the complete lack of schema-level descriptions.

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?

The description clearly states the tool's function: 'Permanently and irreversibly delete this Project' with a specific verb and resource. It differentiates from archive operations by emphasizing irreversibility, and is distinct from delete operations on other entities.

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 description gives context on when to use this tool (for permanent deletion) and warns 'CONFIRMATION REQUIRED', but it does not explicitly mention alternatives like archive_project or specify when NOT to use it. The mention of 'existing Container guards' implies conditions but no direct comparison.

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