cdn_get_cdn_zone

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

Annotations are absent, so the description carries the full burden. It discloses the smart identifier resolution behavior, which is useful. However, it does not explicitly state that this is a read-only operation, what happens on unknown identifiers, or any additional side effects. The description adds some value but leaves gaps.

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 front-loaded: the first sentence states the purpose, the second explains the identifier flexibility, and the Args/Returns sections are minimal. Every sentence earns its place with no redundant content.

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 single-parameter getter with an output schema, this description is largely complete. It covers the main nuance (identifier resolution) and the output schema handles return details. It could mention that the operation is read-only, but the 'get' verb and 'details' make that implicit. Minor gaps in error behavior are acceptable given the low complexity.

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 0%, so this description is the sole explanation for zone_identifier. It clearly documents that the parameter can be an origin domain, CDN domain, or UUID, providing critical semantics far beyond the schema's plain 'string' type.

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 'Get details of a specific CDN zone' with a specific verb and resource. It also adds the smart identifier resolution, which distinguishes this from siblings like cdn_get_cdn_zone_summary or cdn_get_cdn_zone_stats by emphasizing detailed zone information.

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 gives clear context: it retrieves details of a specific CDN zone, and it explains the acceptable identifier formats (origin domain, CDN domain, UUID). However, it does not explicitly say when to prefer this over sibling getters such as cdn_get_cdn_zone_summary, leaving some ambiguity in tool selection.

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