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

Annotations already declare readOnly, idempotent and openWorld, so the safety profile is covered. The description adds genuinely useful context beyond that: cost ('Free'), a docs link, and the shape of the output (gaps weighted blocking/important/to decide across six named parts), which helps the agent interpret results.

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?

A single front-loaded sentence that leads with the action and the returned artifact, then enumerates dimensions. It is dense with product-specific labels ('the door', 'the map') which add length, but each clause earns its place by mapping to an audit area.

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?

There is no output schema, and the description compensates by describing the return value: prioritized gaps across six defined dimensions. Combined with the free/docs pointer, an agent has enough to call and interpret it, though no detail is given on error behavior for unreachable pages.

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% and the single url parameter is fully documented with an example format, so the schema carries the burden. The description adds no syntax or format detail beyond what the schema already provides, making the baseline 3 correct.

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+resource: it runs the GEO SEO Records engine on a public page and returns prioritized gaps. It names the six audit dimensions, so an agent knows exactly what is analyzed. It does not name any sibling, so differentiation from draft_llms_txt or open_robots_txt_to_ai relies on inference.

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?

Implicitly frames usage: it operates on a 'public page' and is 'Free', which tells the agent the prerequisite is a publicly reachable URL. There is no explicit statement of when to choose this over the sibling tools or when it should not be used.

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