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

No annotations, so the description carries the full burden. It discloses the output shape (structural outline, headings, token counts) and the lightweight nature (<200 tokens), which is genuinely useful. It does not explain fetching behavior, failure modes, or how the optional html parameter changes behavior.

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?

A single tight sentence with the value proposition and the <200-token constraint front-loaded. No filler. Slightly dense but every clause earns its place.

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 takes on return-value duty and does describe the outline, headings, and token counts. For a simple 2-param read tool this is close to sufficient; only the html-vs-url interaction and safety profile remain unstated.

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 description coverage is 100%, so baseline is 3. The description adds no parameter-level meaning: it doesn't say when to supply raw 'html' instead of a 'url', nor whether 'url' triggers a fetch. No lift over the schema.

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: 'Returns a <200-token structural outline of any webpage with section headings and token counts.' This is concrete and distinguishable from a full-content tool. However, it never names the obvious sibling (distill_webpage), so the agent must infer the boundary.

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?

'before committing context window budget' implies a recon-first workflow, which is useful usage signaling. But there are no explicit when-to-use/when-not rules and no named alternative, so the choice between this and distill_webpage is left to inference.

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