Delete Project Checklist Template

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

Annotations already provide destructiveHint: true and idempotentHint: true. The description repeats that deletion is permanent, which aligns, but adds little beyond annotations. It mentions the endpoint and required params but no other behavioral traits.

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 redundant: 'This cannot be undone' and 'This action cannot be undone' are repeated, and 'permanently delete the specified Inspections' is stated twice. It could be more concise.

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?

The description does not explain project-level scope, side effects, or response format. For a tool with no output schema and 2 params, it should provide more context, e.g., what happens to associated inspections. Essential information is missing.

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 baseline 3. The description merely lists required parameters 'id, project_id' without adding meaning beyond the schema descriptions. No additional context or constraints are provided.

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?

Description states verb 'Deletes' and resource 'Inspection Checklist Template', but then mentions 'specified Inspections' which may cause confusion between template and inspections. It does not distinguish this from sibling tools like 'delete_checklist_template' or 'delete_company_checklist_template'.

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 says 'Use this to permanently delete the specified Inspections.' It implies usage but does not provide when-not-to-use or alternatives. No guidance on selecting this tool over similar delete tools.

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