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

No annotations are provided, so the description is solely responsible for behavioral disclosure. It describes what the audit checks, but does not state whether the tool is read-only, whether it requires authentication or network access to the target URL, or what format the results take. It never explicitly says the audit causes no modifications, and the word 'audit' only weakly implies a non-destructive operation.

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 entire description is a single, efficiently structured sentence that front-loads the action and uses a colon to itemize the audit's focus areas. Every phrase adds distinct information (What/How/Why headings, FAQ schema, definition snippets) without filler 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?

The description is concise and explains the audit's scope, but for a tool with no annotations and no output schema, it leaves significant gaps: it doesn't explain what the agent should expect after invocation (report, issues list, score), how the target should be formatted for different cases, or how this audit relates to the many sibling audit tools. These omissions make the description adequate but not fully complete.

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 the baseline is 3. The description does not add any parameter-specific details beyond the schema; the target parameter is not mentioned at all, and no syntax, allowed values, or examples are given. There is no value added 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 ('Performs') and a distinct resource ('Answer Engine Optimization audit'), then enumerates the exact audit dimensions (direct answer blocks, question headings, FAQ schema alignment, definition snippets). This clearly distinguishes it from sibling audits like seo_audit_schema or seo_audit_content, even without reading their schemas.

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 implies when to call this tool (when an AEO audit is needed) through its title and scope, but it never states explicit conditions, prerequisites, or alternatives. There is no guidance about choosing this over the overlapping sibling seo_audit_schema or seo_audit_content, leaving the agent to infer usage from the audit type alone.

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