Delete Checklist Schedule

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

Annotations already indicate destructiveHint=true, and the description reinforces this by stating 'This cannot be undone' twice and 'permanently delete'. It also provides the API endpoint and project area (Project Management > Inspections), adding context beyond annotations. No contradictions with annotations.

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 front-loaded with the main purpose and uses clear, direct language. It is mostly concise, though the phrase 'This cannot be undone' appears twice, which is slightly redundant. Overall, it is efficient and structured.

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 delete tool with no output schema, the description covers the key aspects: what it deletes, that it is permanent, required parameters, and the API location. It is sufficient for an agent to understand the tool's impact and requirements.

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 already describes both parameters (project_id and id) with full coverage. The description only lists them as required, adding no additional meaning beyond what the schema 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 the verb 'Delete' and the resource 'Checklist Schedule', and specifies the scope 'in a specified Project'. It also mentions that it deletes 'the specified Inspections', which differentiates it from other delete tools that might delete other entities.

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 explains when to use the tool (to permanently delete a checklist schedule and its inspections) and notes that the action cannot be undone. However, it does not provide guidance on when not to use it or mention alternative tools (e.g., if the user only wants to deactivate instead of delete).

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