delete_project

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

No annotations provided, but description adds critical context: irreversible and cascading delete. Auth category noted. Could mention return value or error handling.

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?

Extremely concise: warning, category/auth/related, and args. Every sentence adds value, no fluff.

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-param destructive tool with no output schema, description adequately covers purpose and key behavior. Could mention result type 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?

Single required parameter project_id. Description minimally clarifies it's the project identifier, but schema has 0% coverage; no format specification (e.g., UUID).

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?

Clearly states verb 'delete', resource 'project', and effect 'all tasks' with strong warning. Distinguishes from sibling tools like list_projects and update_project.

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?

Lists related tools but lacks explicit when-to-use vs alternatives. No exclusion criteria among many deletion-oriented sibling tools.

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