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

Annotations already declare readOnlyHint=false, idempotentHint=false, openWorldHint=true, and destructiveHint=false. The description leans toward read behavior and notes that 'savings are compared with the page's visible text, not its HTML,' a metering/cost detail not in the annotations, but it never explains the charging model or why the call is non-idempotent. Some added context, but thin.

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?

Three short sentences, front-loaded with what is returned and then two constraints. Tight overall, though the 'savings' sentence is cryptic and spends words the agent cannot fully decode.

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 an output schema present, return values need no explanation, and the description covers purpose plus the read_webpage exclusion. The cost/charging behavior around max_sats is the only under-explained aspect for a tool whose annotations mark it non-read-only and non-idempotent.

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 url, max_sats, include_text, and include_links are already fully documented in the schema; the baseline of 3 applies. The description adds nothing to parameters beyond the vague 'savings compared with visible text' note, which does not clarify max_sats semantics.

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 a specific resource set (title, description, OG/Twitter, JSON-LD for a URL), so an agent knows exactly what it extracts, and 'Not for reading the page' distinguishes it from the sibling read_webpage. The verb is only implied (extract/get), so it stops short of a full 5.

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?

The clause 'Not for reading the page' gives one when-not and implicitly routes to read_webpage, but no explicit alternative is named and there is no positive guidance on when this tool is the right choice. Usage is implied rather than stated.

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