score_page

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

Annotations already indicate readOnlyHint=true and destructiveHint=false. The description adds that scores are deterministic and that launching headless chromium happens only when url is provided, which goes beyond annotations without 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 description is thorough but slightly verbose. However, every sentence adds value, and it is well-structured with clear sections for input, output, and comparisons.

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?

Given the complexity (multiple inputs, outputs, relation to audit_page, and guidance for non-mechanical categories), the description covers all necessary context comprehensively. No gaps.

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?

All 4 parameters have schema descriptions, and the description adds meaningful context: url triggers rendering, strict counts warnings as failures, containerMaxWidth is for responsive checks. This enhances the schema info.

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 clearly states the tool scores an HTML/CSS page across 7 design categories with 0–10 ratings, plus an overall score and grade. It distinguishes from audit_page by noting deterministic checks without a browser unless a URL is provided.

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?

Explicitly explains when to pass html directly vs url (triggers headless chromium for rendered DOM). Mentions that brand, conversion, and motion categories are not mechanically assessed and directs users to other tools, providing clear alternative guidance.

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