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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), and the description adds real value beyond them by enumerating the return payload: plain text, cited source links, citation line and CC BY 4.0 license. With no output schema, this is the only place return contents are disclosed; it omits failure behavior for bad ids/URLs.

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 sentences, zero filler, trigger condition front-loaded before the return-value list. Every clause carries information an agent needs.

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?

Return values are covered in the description, which matters since there is no output schema, and the single parameter is documented at 100%. Missing only error/not-found behavior and whether license or citation formatting varies by article.

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% with a single well-described parameter ("Article id or emergetimes.com article URL"), so the baseline is 3. The description adds no format hints, no id/URL tradeoffs, and no example, so nothing beyond the 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?

States a specific verb-and-resource pair: retrieve the full text of a single Emerge Times article. The phrase "one Emerge Times article" implicitly separates it from the discovery-oriented siblings (list_latest, search_articles), so an agent can route 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?

"Use when you need the full text ... to quote, summarize or cite it" gives a concrete trigger condition. It stops short of naming alternatives or stating when not to use it (e.g. use search_articles to find an id first), so no exclusion guidance.

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