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

Annotations already cover the safety profile (read-only, idempotent, non-destructive), so the bar is lower, and the description still adds real context: 'no key' (no auth), 'unknown inputs are named, never zero' (missing-data behavior), and 'a measure of supply, not a forecast of price' (scope boundary). It does not discuss rate limits or pagination across 300 items.

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?

Front-loaded with the core purpose, then the field list, provenance and disclaimers. It is dense but nearly every clause carries information; 'Read-only, no key' slightly duplicates the annotations and 'Not financial advice' is boilerplate, keeping it from a 5.

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?

There is no output schema, but the description enumerates the returned row fields (status, pressure, yearly_pct, pile_24m, next_unlock, etc.) and covers auth and provenance. For a batch tool with zero required params, an agent has enough to call it 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?

Schema coverage is 100%, so the baseline is 3. The description restates the items format ({symbol} or {contract, chain}) and clarifies gem_screener as 'every Gem Screener coin,' but adds little meaning beyond what the schema already documents.

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: 'Many tokens' supply pressure in one call,' and the batch scope is unmistakable. It is clear what the tool computes, though it never explicitly names the single-token sibling supply_analyzer_token to contrast against.

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 describes the two input modes ('items ... or gem_screener=true for every Gem Screener coin'), which gives some selection guidance. However, it never states when to prefer this batch batch vs. supply_analyzer_token, or any exclusions, so routing is left to inference.

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