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

No annotations are provided, so the description carries the full burden. It does disclose what is inspected and what is returned (a score and a prioritized fix list), implying a read-only assessment, but it says nothing about how the page is fetched, whether authentication is needed, or any rate/latency constraints.

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?

Purpose and output are front-loaded, and the dense parenthetical check-list packs meaningful specifics into one sentence without filler. The list is long but every item earns its place as audit criteria.

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 annotations and no output schema, the description must justify the tool on its own. It adequately conveys scope and return content, but omits operational context (live fetch vs. cached, auth, failure modes) that an agent would want before invoking 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 0% for the single url parameter, so the description should compensate. Context makes clear the parameter is the page to audit, but no format, protocol, or required/optional detail is added beyond the implicit 'webpage' reading.

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 names a specific resource (a webpage) and a specific action (auditing AEO/GEO citation readiness), then enumerates the exact signals it checks (crawler readability, answer-first opening, question headings, tables, JSON-LD citation, llms.txt, etc.) and the output (score plus prioritized fix list). This clearly separates it from generic crawler/robots siblings, though it never names an alternative tool.

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 is implied by the enumerated checks, so an agent can infer when it applies, but there is no explicit when-to-use, when-not-to-use, or comparison against neighbors like check_site_crawlers or test_robots_txt.

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