Get Zone

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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true, and openWorldHint=true. The description adds a specific behavioral constraint that the access_key is never returned, which provides additional context beyond the annotations. No contradiction is present.

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 two concise sentences, with the purpose front-loaded and no extraneous information. Every sentence adds value.

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 getter tool with an output schema, the description covers the core purpose and a key behavioral note. However, it could be more complete by briefly mentioning the output_format parameter or error behavior. Nonetheless, given the simplicity, it is mostly sufficient.

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 the description should compensate by explaining parameter semantics, but it does not. While parameter names (zone_id, output_format) are somewhat self-explanatory, no guidance is given on expected formats or values, especially for output_format. The description adds no meaning beyond the schema.

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 the verb 'Get', the resource 'zone (organization)', and the method 'by UUID'. It also includes a unique behavioral detail about the access_key not being surfaced, which distinguishes it from siblings like list_zones or create_zone.

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 implies use when you need a single zone by UUID, but it does not explicitly mention when to use this tool over alternatives (e.g., list_zones, create_zone) or provide any context about when not to use it. The sibling list is extensive but no guidance is given.

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