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

Annotations already declare destructiveHint=true and idempotentHint=false, so the bar is lower, yet the description adds nothing beyond the title. It does not say whether the existing document is replaced wholesale, whether repeated calls differ (non-idempotent), or what permissions are needed for a destructive write.

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?

A single front-loaded sentence with no filler. Nothing is wasted, though the brevity is more under-specification than disciplined concision for a destructive tool.

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 destructive, non-idempotent mutation with a nested config object and no output schema, the description omits whether updates replace or merge existing settings, whether the document must pre-exist, and what the response contains. Annotations carry the safety signal but the description leaves key operational questions open.

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?

Schema description coverage is 100% and both parameters (site_id, nested configuration.badge_style enum) are documented inline, so the baseline is 3. The description contributes no additional meaning about the configuration object or its enum values.

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?

States a specific verb (Update) and resource (Terms & Conditions document) scoped to a site. The resource name cleanly separates it from get_/create_/delete_terms_conditions siblings, though the description never explicitly routes to them.

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 indication of when to use this versus create_terms_conditions or update_privacy_cookie_policy, no prerequisites (does a document already need to exist?), and no exclusions. The agent must infer everything from the name.

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