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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint false. The description adds the crucial behavioral limitation that it does not execute JavaScript or bypass access controls, which is not inferable from annotations. This gives concrete operational context beyond the schema.

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?

Three sentences, each earning its place: purpose, usage constraint, and parameter guidance. No fluff, front-loaded verb, and the key operational detail about JavaScript is placed early. Excellent concise structure.

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 output schema present and only two simple parameters, the description covers purpose, boundaries, and parameter behavior. The read-only, idempotent nature is already captured by annotations, so no additional disclosure is needed. The tool is fully specified for correct invocation.

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 baseline is 3. The description repeats the schema's 'absolute public HTTP(S) URL' and fresh/cache guidance, adding no new meaning beyond what the schema already specifies. It does reinforce the public/resource constraint, but the marginal value is minimal.

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 opens with a specific verb and resource: 'Report evidence-backed framework, CMS and generator signals.' This clearly distinguishes it from sibling tools like web.url.headers or web.url.links, which address different signals. The scope is unambiguous.

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 guidance is explicit: 'Use only for public HTTP(S) resources' and 'does not execute JavaScript or bypass access controls' sets a clear boundary. The fresh parameter behavior is explained, though it does not explicitly compare to alternative tools. Still, the context is sufficient for selection.

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