inspect_viewport_meta

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

No annotations provided, so description carries full burden. It explicitly lists the issues reported (missing width=device-width, disabled zoom, missing viewport-fit=cover, common misconfigurations), giving a clear behavioral outline.

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, no filler. First sentence states purpose, second lists specific outputs. Every word contributes value.

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 no parameters and no output schema, the description is complete. It fully explains what the tool does and what it reports, with 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?

Zero parameters and schema coverage 100% means description does not need to add parameter details. Baseline 4 for zero params; description is concise and sufficient, earning a 5.

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?

Description uses specific verb 'Parse and validate' and clearly identifies resource 'viewport meta tag,' listing specific issues (missing width=device-width, disabled zoom, missing viewport-fit=cover). This distinguishes it from sibling tools like extract_meta or check_ios_web_app_readiness.

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 description clearly states when to use the tool (to validate viewport meta tag against iOS Safari best practices). However, it does not explicitly mention when not to use it or provide alternative tools, though the unique focus makes context clear.

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