Check server-rendered HTML

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

Beyond the readOnlyHint annotation, the description discloses a key behavioral trait: it fetches without executing JavaScript. This is non-obvious and adds context about how the check works and what it detects. It also explains the practical implication for search engines/AI, which is valuable behavioral context.

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 a single sentence that is concise and front-loaded with the main action ('Fetch a page without executing JavaScript'). Every phrase adds value, with no redundant or filler content.

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?

For a simple tool with one parameter and no output schema, the description covers the essential purpose and behavior. It could optionally describe the return format, but that is not necessary for understanding what the tool does. The context about Google/AI interpretability adds completeness.

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?

The input schema already has 100% coverage with a clear description for the single 'url' parameter. The tool description does not add additional parameter-specific semantics, so the baseline score of 3 is appropriate given the schema's completeness.

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 uses a specific verb ('fetch', 'detect') and resource ('server-rendered HTML vs client-side JS shell'), clearly distinguishing it from sibling audit tools that check different aspects like URL structure or HTTPS. It unambiguously states what the tool does.

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 implies the tool is for checking rendering behavior and why it matters ('hard for Google/AI to interpret'), giving clear context for when to use it. However, it does not explicitly mention alternatives or exclusion criteria, though none of the sibling tools directly overlap with this specific rendering check.

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