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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered. The description's one added behavioral fact is the 'public' qualifier, implying only public pages are reachable — useful but thin; with an output schema present it need not describe return format.

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 short sentences, no filler, with the purpose (what is returned) front-loaded before the usage pointer. Every clause carries information.

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?

A single required parameter at 100% coverage, rich annotations and an output schema mean almost nothing else needs saying. The only small gap is unstated behavior for invalid paths or pages that are not public.

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% for the single 'path' parameter, and the schema already says 'Site path from list_pages, e.g. /indicators; 1–2048 characters.' The description only restates the list_pages origin, adding no syntax or format detail beyond the schema, so the baseline 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 a public Altair page's full markdown') and enumerates what comes back (path, URL, title, description). It implicitly separates itself from list_pages by being the content-retrieval step, but never explicitly distinguishes itself from read_research_report, the other 'read' sibling.

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 a path from list_pages when you need the page content' gives an explicit prerequisite and the condition that selects this tool over list_pages. There is no statement of when-not to use it (e.g. for non-public or report content), so it stops short of full routing guidance.

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