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

Beyond the readOnly/openWorld annotations, the description discloses the per-call price, that unknown ids are not charged, the required Authorization: Bearer API key on the connection, and the 100-call/7-day free window. These are precisely the operational facts an agent needs before spending money or hitting an auth failure.

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 dense sentences: the first front-loads what is returned and the id source, the second packs cost, error-billing behavior, auth, and free-tier limits. No filler and nothing important is buried.

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 one-parameter read with an output schema, the description covers the remaining agent-relevant concerns: where the id comes from, what the response contains, auth requirements, and cost/billing edge cases. Nothing needed to invoke it correctly is missing.

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% and the single parameter already carries the 'id of a list_news record' description, so the description largely restates it. It adds no new syntax, format, or constraint detail beyond the schema, which is the expected baseline here.

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 is fetched (one news article), the key it is fetched by (article_id), and what comes with it (all the quorums on its story). It also anchors the id to a sibling tool, list_news, so an agent can distinguish this from list_news and search_quorums without opening a 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 makes the calling path clear: the id must come from a list_news record, which tells an agent to list before getting. It does not name an explicit alternative or exclusion (e.g., when to use get_quorum instead), so it falls short of full when/when-not guidance.

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