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

Annotations only cover the safety profile (read-only, idempotent, open-world, non-destructive), and the description adds substantive context beyond them: fetch-only methodology, no-JavaScript rendering limitation, a daily per-site rate limit, and the response shape (findings with title and tier, all checks with results, fullReport link emailed). This is well past the lowered bar annotations set.

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?

Front-loaded with purpose and scope in the first clause, and every clause carries information an agent needs (constraints, limits, output shape, exclusions). It runs long as a single dense passage with some repetition around the 'no account' theme, but there is little that could be cut without losing decision-relevant detail.

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 no output schema, the description carries the return-value burden and does so: findings with titles and tiers (Blocker first), every check performed with its result, and a fullReport link delivered by email. Combined with the rate limit and account boundary, an agent has everything needed to call and interpret it.

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 single url parameter is already fully documented in the schema with format examples. The description adds only the constraint that the target must be one public site per call, which is marginal added meaning over the schema.

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?

States a specific verb (checks) and resource (one public website's readiness for AI search), then enumerates the actual dimensions checked: crawler allowances, JS-free readability, structured data, titles/descriptions, llms.txt. There are no siblings, so no differentiation is needed, and the scope ('one site per call') 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?

Gives clear context (free, no account required, one site per call) and an explicit exclusion: it does not ask AI engines whether the business is named or cited, which requires an account. No alternative tool is named because none exists, so the when-not guidance is as complete as the toolset allows.

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