delete_project

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

With no annotations, the description fully discloses the destructive behavior ('PERMANENTLY delete', 'DESTRUCTIVE'), the confirmation requirement, and the return value format { ok: true, project_id }.

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 front-loading the core action and critical warnings. Every sentence adds necessary information with zero 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?

Despite no output schema, the description covers all essential aspects: action, scope, destructive nature, confirmation requirement, and return value. No gaps for a deletion tool with well-documented parameters.

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%, but the description adds critical context beyond the schema by emphasizing the destructive nature and the exact confirmation requirement ('Must be exactly true'), which is not fully captured in the schema description alone.

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 specifies 'Permanently delete a Kanboard project' and lists all associated items (tasks, columns, swimlanes), distinguishing it from sibling deletion tools like delete_task or delete_column.

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?

Explicitly states the destructive nature and the requirement for 'confirm: true', guiding appropriate usage. Does not explicitly mention when to avoid this tool or alternatives, but the confirmation flag serves as a strong situational cue.

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