taiga_projects_delete

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

With no annotations provided, the description carries the full burden of disclosing behavioral traits. It only says 'Delete a project,' implying a destructive action, but does not state whether it is permanent, whether it cascades to related entities (epics, user stories, tasks), or whether special permissions are required. This is a significant transparency gap for a mutation tool.

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 a single sentence that directly states the action and the required identifier. Every word earns its place, with no redundancy or filler. It is appropriately sized for a simple one-parameter tool.

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?

Although the tool has only one parameter and no output schema, it is destructive. The absence of any note about permanence, side effects, or authorization makes the description incomplete for safe and correct use. For a delete operation, the context is not sufficiently covered by the schema or annotations.

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 100% because the only parameter 'id' is already described as 'Project ID.' The description's phrase 'by its ID' merely rephrases the schema and adds no extra information about format, constraints, or usage. Baseline 3 is appropriate when the schema handles parameter documentation adequately.

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 verb 'Delete' and the resource 'project' with the means of identification ('by its ID'). It distinguishes from sibling tools like taiga_projects_update, taiga_projects_get, and taiga_projects_create, and even from taiga_projects_delete_tag which deletes a different entity.

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 no guidance on when to use this tool versus alternatives, no prerequisites, no exclusions, and no warning about irreversibility. For a destructive operation, some usage context should be provided, such as verifying the project ID first or noting that deletion may have cascading effects.

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