delete_projects

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

Labels the action as DESTRUCTIVE and describes the response structure, but with no annotations and no mention of prerequisites, side effects, or permission requirements for a destructive operation.

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 sentences, no wasted words, front-loaded with purpose and key traits.

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?

Handles the lack of output schema by describing the response, but could add context on when to delete vs close or other constraints for a more complete picture.

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%, so the description adds limited parameter-specific meaning beyond stating the array-based nature and destructive flag; minimally enhances what the schema already provides.

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 deletes projects, specifies it is array-based and destructive, and distinguishes from sibling tools like close_projects or batch_delete_work_items.

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?

Mentions single-item and batch use share the same interface, giving implied usage context, but lacks explicit guidance on when to prefer this over alternatives like close_projects or recover_deleted_items.

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