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

The description does not disclose side effects, idempotency, partial vs. full replacement semantics, or any validation behavior. Annotations provide no behavioral hints beyond non-read-only, non-destructive, non-idempotent stances.

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 and free of extraneous content. It uses a single clear sentence.

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 tool is simple, and the schema provides basic parameter names, but important context is missing, such as whether the configuration replaces the entire document or just updates certain fields, and what the expected response is.

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 parameters have descriptions, but they are minimal. 'site_id' is just 'Site ID' and 'badge_style' is 'Badge visual style' without explaining allowed values or their meaning. The configuration object's intended structure is only partially conveyed.

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 clearly states the action ('Update') and the resource ('Terms & Conditions document for a site'), distinguishing it from sibling create/delete/get operations.

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 guidance is provided on when to use this tool versus alternatives, such as create_terms_conditions or update_site. The verb 'update' implies modification of an existing resource, but explicit when/when-not conditions are absent.

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