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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds value beyond that: it requires the page to be LIVE/published (a real precondition failure mode) and states the return format is markdown. It does not explain why idempotentHint is false for what reads like a pure read, or how long a full audit takes.

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?

Two sentences, both front-loaded: what you get first, then the lifecycle guidance. No filler, no restatement of the tool title, and the return format is tacked on efficiently at the end.

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?

No output schema exists, so the description carries the burden of the return value and does so by naming the scoring dimensions and 'markdown'. Complete enough to decide to call it, though it omits what happens when the page is not published and gives no sense of report size or cost.

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?

Only one parameter (pageId) with 100% schema description coverage, so the schema already explains its meaning. The description reinforces that pageId must reference a published page ('LIVE published page'), which is the one semantic nuance the schema lacks, but adds no format or failure behavior beyond that. Baseline 3 is right when the schema does the heavy lifting.

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?

Specific verb and resource ('Audit a LIVE published page') plus the concrete output: a scored, prioritized report across five named dimensions. Explicitly scopes itself to published pages, which distinguishes it from draft-oriented siblings like get_draft_html or get_page_information.

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 an explicit when: run it while improving a page before it has traffic. Also names the alternative and the condition that selects it — pair with get_analytics once the page has traffic. That is exactly the when/when-not/alternative structure an agent needs.

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