Delete A Compliance Document.

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

Annotations already mark destructiveHint=true and readOnlyHint=false. The description reinforces the irreversible nature ('cannot be undone') and provides the exact HTTP method and endpoint, adding context beyond annotations. No contradiction.

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 very concise: three sentences conveying purpose, permanence, and API reference, plus a note on required parameters. No unnecessary words.

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 three parameters and no output schema, the description covers the essential action, consequences, and API details. The annotations provide additional safety hints. It lacks explicit success response info but that is typical for DELETE endpoints.

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?

All three parameters have schema coverage at 100%. The description simply lists the required parameters without adding semantic meaning beyond what the schema already provides (URL path parameters).

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 tool name and title clearly indicate deletion of a compliance document. The description specifies it's for permanently deleting Commitments, referencing the precise API endpoint. Among numerous sibling delete tools, this one is uniquely identified by its resource type and version.

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 states the action and its irreversibility but does not guide when to use this tool over alternative compliance document deletion tools (e.g., delete_a_compliance_document_project or delete_requisition_compliance_document). No explicit when-not-to-use or alternative differentiation.

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