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

Beyond annotations, the description discloses sanitisation rules (no scripts/styles/frames/forms/event handlers; links and https images survive), content moderation, storage, noindex serving, expiry limits, pricing ($0.01/call), failed-call policy, and repeat-call cost. These are substantive behavioral details an agent could not infer from annotations alone.

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 paragraph is dense but front-loaded: purpose and return format come first, then behavioral constraints and pricing. Every sentence carries operational information, though the pricing/support details make it slightly overstuffed for a single paragraph.

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 no output schema, the description still explains what the caller receives (a public URL at /p/<id>) and the page's lifetime. Annotations cover the safety profile, and the description fills in sanitisation, moderation, and cost behavior. An agent has enough to invoke this correctly.

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 schema already documents html, title, and days with defaults and limits. The description mostly repeats those constraints ('up to 200,000 characters', 'optional title', 'valid up to 7 days') rather than adding new syntax or edge-case semantics. 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?

The description states a precise verb+resource ('Publish an HTML page and get a public URL') and clarifies scope: sanitisation, moderation, storage, and serving at /p/<id>. This is clearly distinguishable from every sibling tool, which are extraction/research utilities rather than output-hosting tools.

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?

It gives clear when-to-use guidance: 'hand a person a report, table or summary your agent produced, or to share results between agents.' It does not name explicit alternatives or exclusions, but the intended context is unambiguous.

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