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

Annotations only cover the safety profile (readOnlyHint=true), so the description's disclosure that secrets (token-auth key, AWS signing secret, certificate private keys) are redacted is genuinely additive and prevents false assumptions about returned data. It also notes the underlying GET endpoint, aiding error interpretation.

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?

Two dense sentences, zero filler. The high-value information (scope of returned settings, secret redaction) is front-loaded before the endpoint annotation.

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?

With no output schema, the description compensates by enumerating the returned setting families, and it flags redaction and the edge-rule GUID linkage. Nothing an agent needs to call and interpret this read correctly appears to be missing.

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%, so both parameters are already documented and the baseline is 3. The description reinforces certificate/secret handling but adds no syntax or format detail for include_certificate or pull_zone_id beyond what the schema provides.

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 and resource ("Fetch one pull zone") and enumerates the setting families returned, which cleanly separates it from the plural sibling bunny_list_pull_zones. An agent can distinguish the two without opening either schema.

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?

Gives clear retrieval context and a workflow hook by noting the edge-rule GUIDs are 'needed by bunny_set_edge_rule_enabled', which tells the agent how this tool chains into a mutation. It stops short of explicit when-not guidance (e.g. using list_pull_zones to discover the ID first).

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