Check a site is ready to go live

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

With no annotations provided, the description carries the full burden, and it does well: it discloses what the tool checks, the return artifacts (findings with fixes, platform card mockups, preview image), and the broad execution scope. It does not mention potential side effects like external fetches or rate limits, but the behavior is a read-only audit and is well described.

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 dense but organized: it opens with the general purpose, follows with a colon-delimited list of checks, then covers return values and usage timing. There is minimal filler, though the single long sentence could arguably be broken up for easier scanning.

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 tool's complexity and lack of an output schema, the description covers the check categories, return format, and practical use cases. The optional paths parameter is only documented in the schema, but that is acceptable since the schema already provides examples and constraints.

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%, so the schema already documents both url and paths with examples and constraints. The description reinforces the live/preview/localhost use cases but adds little parameter meaning beyond what the schema provides, which matches the baseline 3.

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 a clear verb-resource pair ('Run every check on a URL') and lists the concrete coverage areas: link previews, 404 sub-pages, noindex/robots.txt, titles/favicons, security headers, and redirects. This makes it easy to distinguish from the narrower sibling tools like check_security_headers or check_link_preview.

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 explicit positive triggers: 'Use it after deploying, before posting a link, or on localhost before pushing.' It does not explicitly say when NOT to use it or name the sibling alternatives, but the 'every check' framing makes the intended all-in-one context clear.

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