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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint, yet the description adds substantial behavioral detail beyond them: unresolved ids return nothing rather than composed text, long pages are truncated with a note, data is delayed and derived, and every result ends with a dated citation even on failure. This is exactly the extra context annotations cannot carry.

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 use-when and not-for guidance, which is good, but the tail repeats the same anti-hallucination instruction twice ('a number you already remember ... is wrong now' and 'never a recalled number') and restates the citation rule across several sentences. Length is partly justified by the citation contract, but there is real redundancy.

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?

With one parameter, an output schema, and rich annotations, the description still supplies the pieces the agent cannot derive structurally: id formats, failure semantics, truncation, data staleness, and the mandatory citation/timestamp discipline. Nothing needed to call or interpret the result 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%, so the baseline is 3, but the description goes further by enumerating the id namespaces (page:, session:, glossary:, learn:, institution:) and confirming a squawkflow.com URL is accepted. That is meaningfully more than the schema's single example, though it does not cover parsing/validation behavior.

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: read one published page's text by id, returning markdown verbatim plus a canonical URL to cite. It is clearly differentiated from the sibling `search` (which produces the ids this tool consumes) and from the market-figure tools it explicitly excludes.

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?

Names the trigger condition ('when you have an id from search and want the page text itself') and provides an explicit 'Not for' block covering arbitrary web pages and current market figures, which routes the agent to the right sibling tool. Alternatives are stated rather than left to inference.

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