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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. With no output schema, the description adds real value by disclosing the response shape (a shields.io endpoint payload) — information an agent could not get from structured fields.

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 short sentences, front-loaded with the output format and purpose, with no filler. The metric enumeration is slightly redundant against the schema enum but is compact and readable.

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 single-parameter, read-only tool with no output schema, the description covers the essential context: what is returned (badge payload), why (live README figures), and the selectable metrics. Missing only per-metric semantics and sibling routing, which keeps it out of 5 territory.

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 0%, so the description must compensate. It lists the metric values, but that list simply mirrors the enum already in the schema and gives no meaning for each metric (e.g. what volume30 counts or what period 'makers'/'pairs' represent), nor does it mention the volume30 default.

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 names the concrete output ('a shields.io endpoint payload for the catalogue metrics') and its consumer (a README badge), which is specific enough to distinguish it from siblings like trdefi_stats or trdefi_chains. It is clear but never explicitly contrasts itself with those siblings.

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?

Usage is only implied via 'so a README can show live figures' — an agent can infer this is for embedding badge values, not for querying analytics data. There is no explicit when-to-use / when-not-to-use or pointer to trdefi_stats for raw figures instead of badge payloads.

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