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

With no annotations, the description carries the behavioral burden and does disclose important access behavior: x402 payment versus API-key authentication, including per-call cost. It does not explicitly state read-only status, rate limits, or pagination behavior, but for a zero-parameter listing tool the access disclosure is the main missing-risk information.

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 front-loaded with the core purpose and return fields, followed by a clear usage rule. The bracketed access note is compact and earns its place by explaining payment/authentication requirements.

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 zero-parameter list operation, the description covers purpose, return metrics, usage guidance, and access requirements. Since there is no output schema, it could more fully describe the response shape, but it gives enough for an agent to call the tool correctly.

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?

The tool has zero parameters, so there are no parameter semantics to clarify. The baseline score of 4 applies because the description does not need to explain inputs and the schema is already empty.

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 states exactly what the tool returns: every exchange tracked by Mangrove, including tier and 24h volume. It also distinguishes the scope from a single-venue lookup, making it easy to separate from siblings such as get_symbol_exchanges.

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 gives an explicit use case: when the user asks what exchanges are supported or wants to browse the exchange universe. It also names the contrasting condition, 'rather than a single venue,' which routes the agent away from venue-specific tools.

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