GEO readiness score of a page

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false. The description adds valuable context beyond these by listing the exact signals analyzed (FAQ schema, E-E-A-T, outbound citations, etc.) and disclosing the return payload (score, signals found, and concrete fixes). This gives the agent a clear picture of what the tool does internally.

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 compact and front-loaded: the first sentence opens with the main verb and purpose, then efficiently lists the evaluation criteria, and the second sentence states the return values. Every phrase adds useful information without fluff or repetition.

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 single-url, read-only scoring tool, the description covers the input, the process, and the output clearly. It lists the page attributes examined and the concrete returns (score, signals, fixes). Minor omissions like score interpretation or accessibility prerequisites are acceptable given the tool's simplicity and the absence of an output schema.

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%, so the description must compensate for the undocumented url parameter. It only implicitly ties the parameter to 'a page' without explicitly stating that the url should be the page to score or specifying format constraints. Since there is only a single, self-explanatory parameter, the gap is small, but not fully bridged.

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 ('Score'), identifies the resource (a page's GEO readiness for AI answer engines), and enumerates concrete evaluation signals. It clearly distinguishes this tool from generic audits like page_audit or eeat_audit by focusing on extractability/citability by ChatGPT, Perplexity, and Google AI Overviews.

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 clearly implies the use case: use this when you need a 0-100 GEO readiness score and insights into how AI answer engines can extract and cite a page. However, it does not explicitly name alternative tools or state when not to use it, so it falls just short of full guidance.

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