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

Annotations already declare this a safe, idempotent, non-destructive, closed-world read, so the safety profile is fully covered elsewhere. The description adds only the return format ('clean markdown text') and the constraint that the page be 'published'; it says nothing about auth, size limits, or behavior on unpublished 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?

One short, front-loaded sentence with no filler; the key fact (markdown text of a published page) is stated immediately. It reads as a fragment rather than a full sentence, but nothing is wasted.

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 full annotation coverage and 100% schema coverage, the description supplies the one thing the structured fields don't: the shape of the return value. Error cases (unpublished, invalid path) and the absence of an output schema are the only remaining gaps, which are minor here.

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?

There is a single parameter with 100% schema description coverage ('A URL or path on com.bot'), so the schema carries the semantics. The description adds nothing about the url argument beyond reiterating 'published page', which earns the baseline 3 rather than more.

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 names the resource and the return format precisely: the 'clean markdown text' of a 'published page on com.bot'. That is enough for an agent to know what it yields, though it never states an explicit verb and does not distinguish itself from siblings like search_site or ask_question, which also surface page content.

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?

There is no when-to-use guidance at all. With siblings such as search_site, ask_question, and get_brand_facts all plausibly answering questions about com.bot content, the description should say when to fetch a raw page directly versus searching or asking, and it does not.

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