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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint=false. The description adds useful behavioral context beyond them: robots.txt compliance, public-page restriction, 1h cache, and sha256 of returned content. The paid HTTP and referral details are not needed for invocation and do not explain errors or rate limits beyond caching.

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?

The first sentence is front-loaded and efficient, but the paid HTTP endpoint and lengthy referral-program details are promotional and mostly irrelevant to tool selection or invocation. They dilute an otherwise concise definition.

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 simple two-parameter tool with full schema coverage and rich annotations, the description covers the core behavior, output shape, robots.txt constraint, cache, and public-page scope. The missing maxChars semantics are handled by the schema, though the referral/payment text is extraneous rather than completing invocation context.

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 both url and maxChars documented in the schema. The description only echoes the public URL constraint and does not mention maxChars or truncation behavior, so it does not add meaning beyond the schema. Baseline 3 is appropriate.

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: fetch a public web page and return clean Markdown with title, headings, links, lists, code, and sha256. The output shape is clear, and the sibling tools are unrelated, so an agent can identify this as the page-to-Markdown tool without ambiguity.

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?

Gives clear applicability constraints: public pages only and robots.txt respected. It does not explicitly name alternatives or when-not-to-use beyond the public-page restriction, but the sibling tools do not overlap with this capability.

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