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

Annotations already cover read-only, idempotent, open-world, non-destructive. The description adds real value beyond them: source provenance (GitHub releases, project announcements, reputable RSS), the 'strongly filtered to the agent economy' scoping, and the emphasis on dated/source-attributed over undated blog posts. It stops short of discussing freshness/latency or dedup behavior.

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 trigger condition, then a NOT FOR exclusion, then RETURNS and a concrete example. Every block is short and earns its place; no filler.

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 compensates with a full RETURNS block enumerating every field (total, count, offset, has_more, next_offset, and the news item fields). Combined with filter and pagination guidance, an agent has everything needed to call and interpret this 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 description coverage is 100%, so the schema already documents kind, chain, limit, offset, and response_format. The description restates these ('filter by kind ... and/or chain; paginate via limit/offset') with a worked example, adding only the minor point that kind and chain are combinable ('and/or'). Baseline 3 is appropriate.

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 (fetch dated, source-attributed news/releases in crypto AI agents) and explicitly distinguishes itself from siblings by naming onchain_agent_recent_changes and onchain_agent_get_wiki_page. An agent can tell what this returns versus those two without opening any schema.

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 opens with an explicit 'USE WHEN' trigger and a 'NOT FOR' clause that names both alternatives and the conditions that select them. The kind/chain filter and pagination guidance further pin down correct invocation.

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