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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered without the description. The description adds a useful fidelity guarantee ('markdown with code listings preserved verbatim') and implies full, untruncated text, but says nothing about failure modes for bad ids, paywalled content, or size limits. Since an output schema also documents the return shape, the remaining added value is modest.

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?

One sentence, front-loaded with the action and resource, with the id provenance and output format folded in as compact parenthetical and trailing clauses. No filler or restatement of the tool name beyond what is needed.

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 tool with an output schema and full annotations, the description covers what is needed to call it correctly and what form the content arrives in. Only edge-case behavior (invalid id, truncated long articles) is left unaddressed, which is a minor gap given the structured fields already present.

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?

With a single parameter at 100% schema description coverage, the schema already fully documents 'id' as the canonical URL from search. The description restates the same meaning rather than adding format, validation, or fallback guidance (e.g., whether a slug is acceptable), so the baseline of 3 applies.

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 ('Return the full text of one article') and constrains the scope to a single item retrieved by id, which clearly separates it from a search/list operation. The parenthetical tying the id to search results makes the relationship to the sibling search tool explicit.

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?

Tells the agent exactly where the required id comes from ('from search results'), establishing the search-then-fetch workflow. It does not say when not to use it (for example, whether get_page is the right choice for non-article pages), so the guidance is clear but not exhaustive.

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