Delete Company Checklist Template

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

The description emphasizes that the deletion is permanent and cannot be undone, which goes beyond the destructiveHint annotation by repeatedly warning about irreversibility. This provides clear behavioral transparency. No contradiction with annotations is present.

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 concise but contains repetition: 'cannot be undone' is stated twice and 'permanently removes' twice. The inclusion of Procore API details is extra but adds context. Slightly more concise could improve score.

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 simple delete operation with two parameters, the description covers the action, irreversibility, required parameters, and API endpoint. No output schema exists, so no need to explain return values. The description is complete enough for an agent to invoke correctly.

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?

The schema covers 100% of parameters with clear descriptions. The description lists required parameters but adds no additional meaning beyond what the schema already provides. Baseline score of 3 is appropriate.

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 'Delete Company Checklist Template' and specifies the action is permanent. However, it repeatedly refers to 'the specified Inspections' which could cause confusion since the tool deletes a template, not inspections directly. The name and description together are sufficient to distinguish from sibling delete tools.

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 lacks explicit guidance on when to use this tool versus alternatives. It does not mention any prerequisites, conditions for use, or scenarios where another tool should be preferred. Only the action and permanence are stated.

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