get_dns_secondary_zone

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

No annotations are provided, but the description only says 'Get details' with no disclosure of permissions, rate limits, or what 'details' entails. For a read operation, more behavioral context (e.g., requires zone ID, returns full zone object) is missing.

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, clear sentence with no extraneous text. Every word contributes to the purpose.

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?

Given no output schema and many sibling tools, the description should indicate return details (e.g., zone name, MNAME), but does not. It fails to provide enough context for an agent to understand the full scope.

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 coverage is 100% with 'secondary_zone_id' described as 'the ID of the secondary DNS zone'. The description adds no additional meaning beyond the schema, so baseline 3 applies.

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 'Get details of a specific secondary DNS zone' uses a specific verb 'get' and resource 'details of a specific secondary DNS zone', clearly distinguishing it from sibling tools like 'list_dns_secondary_zones' (listing) and 'get_dns_secondary_zone_axfr' (AXFR transfer).

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 on when to use this tool versus alternatives (e.g., list_dns_secondary_zones, get_dns_secondary_zone_axfr). The description lacks exclusions or context for selection.

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