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

The annotations already declare readOnlyHint=true, so the safety profile is covered, and the description usefully enumerates the returned statistics. However, it does not note the idempotentHint=false characteristic or any freshness/polling behavior an agent might care about for a congestion-monitoring tool.

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 tight sentences with the return content front-loaded and the usage cue trailing. No filler or repetition.

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 no-param read tool whose annotations carry the safety profile, the description adequately covers the output metrics (compensating for the absent output schema). It is nearly complete, only missing any note on data freshness or whether the metrics are point-in-time.

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?

Zero parameters with 100% schema coverage, so the baseline of 4 applies. There is nothing for the description to clarify on the input side.

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 uses a specific verb+resource ('Returns queue statistics') and enumerates the exact metrics returned (pending swap count, outbound transaction count, internal queue size, scheduled outbound value). This lets an agent distinguish it from bare siblings, though it does not explicitly differentiate itself from the many other queue-related tools (get_outbound_queue, get_scheduled_queue, get_swap_queue).

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?

It provides one usage cue ('Use this to understand network congestion'), which gives context but no when-not guidance or alternatives. Given the cluster of sibling queue tools, an agent still has to infer which queue endpoint fits which scenario.

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