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

The description's 'Delete' matches the destructiveHint=true annotation without contradicting any annotations. It adds useful scope by clarifying that the target is a per-site Terms & Conditions document, but it does not disclose permanence, cascading effects, or failure behavior. Since the annotation already conveys destructiveness, the description provides minimal extra behavioral context.

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, compact sentence of nine words with no filler. The action, target, and scope are all front-loaded, making it immediately understandable.

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 one-parameter delete operation, the description, schema, and annotations together provide enough information to invoke the tool correctly. The resource scope is clear, the destructive behavior is flagged, and the required site_id is documented. A minor gap is the lack of any statement about the expected response or lack thereof, since there is no output schema.

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 input schema has 100% description coverage for site_id, so the schema fully documents the parameter. The tool description does not add any extra meaning about the parameter beyond what the schema provides. Baseline 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 states exactly what the tool does: it deletes the Terms & Conditions document for a site. The verb 'Delete' and the specific resource scope clearly distinguish it from sibling tools like create_terms_conditions, get_terms_conditions, update_terms_conditions, and delete_site.

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?

No explicit guidance is given about when to use this tool versus alternatives such as update_terms_conditions or get_terms_conditions. There are no prerequisites, exclusions, or side-effect warnings; usage is only implied by the verb 'Delete.'

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