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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false plus openWorldHint=false. The description adds useful behavioral context by labeling the data as 'published transparency data' and specifying what categories the agent will receive. For a parameterless read operation, there is little hidden behavior left to disclose.

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 concise sentences with no filler: the first lists the data categories, and the second gives the audit use case. Everything earns its place.

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 zero-parameter, read-only metadata tool, the description plus annotations fully orient an agent: it knows what the tool returns, why to use it, and that it is safe/non-mutating. No output schema means additional format details could help, but the stated data categories are sufficient for correct invocation.

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 the input schema already fully conveys parameter semantics. The description appropriately focuses on the data content rather than repeating an empty 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 states a specific verb and resource ('Get treasury + router allowlist') and enumerates the exact data contents: treasury addresses, router allowlist, fee schedule, and paused venues. This clearly distinguishes it from the sibling swap/quote/route tools.

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 explicitly says 'Use this to audit quotes and transactions,' giving a clear context for when to invoke the tool. It does not name alternative tools or exclusions, but no sibling appears to offer equivalent audit data, making the intended usage unambiguous.

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