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

Adds genuinely useful behavior beyond the annotations: quota consumption ("Counts against the plan's daily limit"), consent not required, and a prompt-injection warning about external data. However, the "[When to use]" block claims the tool "changes data or sends notifications," which mischaracterizes an analysis/read operation and contradicts the same description's "nothing is taken." Annotations (readOnlyHint=false, openWorldHint=true) technically leave room for the write framing, so this is an internal inconsistency rather than a direct annotation contradiction.

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 return/exclusion enumeration is front-loaded and earns its space, but the trailing "[When to use]" paragraph is boilerplate that both wastes length and injects a wrong characterization of the tool.

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 carries the return-shape burden well by enumerating every returned field group and the exclusions. Quota and consent behavior are also covered. The misleading when-to-use block is the only missing/wrong piece an agent needs to call it 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 description coverage is 100% — url, site and pages are each documented in the schema, including the 1-3 page cap and default. The description adds no parameter-level meaning (e.g. how many pages to read for a design audit), so the schema carries the full load.

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 precisely what is extracted (palette with hex/roles, fonts, layout, tone metrics, meta) and, unusually, what is deliberately excluded (no text, images, logos or links). No sibling tool does anything comparable, so it is easy to place. It stops short of a clean verb phrase ("The look of..."), which keeps it from a 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?

It gives a downstream-purpose constraint ("use the result only to choose colours, fonts and structure for the person's own site") but no real guidance on when to pick this over fetch_site or other read tools. The "[When to use]" block is generic boilerplate rather than guidance specific to this tool.

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