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

Annotations already declare readOnlyHint=true and openWorldHint=false, and the description adds real substance on top: output is Markdown, platform-specific content falls back to a general version, and passing consent_tool entirely changes the returned guide. It does not say what happens for an unrecognized issue_id or whether a missing guide errors or returns empty.

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 behavioral core is front-loaded in the first two sentences, but nearly half the description is a dense comma-delimited run of 27 dot-notation ids buried in prose, which is hard to scan and would be better as a structured list or schema enum. The content earns its place; the formatting does not.

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 burden of describing the return value and does so (Markdown guide). It covers platform fallback and consent-tool behavior. The only missing piece is failure behavior for an unknown or unsupported issue_id.

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 baseline is 3, but the description genuinely adds meaning: it enumerates the full valid set of issue_id values (27 problem guides plus 4 setup guides) rather than just the one schema example, and it explains the conditional interaction between platform and consent_tool that the schema cannot express.

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 step-by-step Markdown fix guide for a problem a check found, with platform-specific and consent-tool variants. It is clearly distinct from check_page/get_report/list_findings, though it never names a sibling to route away from.

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?

Usage context is clear: pass an issue_id produced by a check report, and optionally a consent_tool to get the pixel-wiring guide instead. It also explains the platform-vs-general fallback. There are no explicit 'when not to use this' exclusions, so it stops short of a 5.

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