delete_project

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

Discloses irreversibility and default session behavior. However, no annotations exist, so description should cover side effects (e.g., cascading deletion of related data) but does not.

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 concise sentences with no extraneous information. Front-loaded with purpose.

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 tool, lacks critical context: data impact, permissions required, or confirmation steps. Output schema exists but not described. Minimal for 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?

With 0% schema coverage, description adds minimal meaning: explains project_id is the ID and session_id defaults. Does not specify ID format or exact session_id usage.

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?

Clear verb+resource: 'Deletes a project by its ID.' Distinguishes from create, update, and get operations among many siblings. Irreversibility adds emphasis.

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?

Implied usage: use when you want to delete a project. No explicit when-not-to-use or alternative suggestions. Lacks prerequisites or considerations.

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