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

The description claims a 'technical SEO audit' which inherently implies a non-destructive, read-only operation. However, annotations declare destructiveHint=true and readOnlyHint=false. The description does not disclose any destructive side effectchers—this contradicts the annotation, hence the score of 1.

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 two sentences with the core purpose front-loaded. The first sentence lists outputs, the second gives price and authorization requirement. No unnecessary words and easy to parse.

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 covers the audit scope and payment requirement, but with no output schema and five parameters including signatures, it fails to explain the authorization flow or how the signatures map to the stated wallet authorization. An agent may not know which fields are required for a successful payment or how to construct them. Partial completeness.

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%, and the description only references a 'URL,' while the schema defines both 'url' and 'domain' as alternatives. It does not explain the purpose of payment_signature, idempotency_key, result_expires, or result_signature, leaving the agent to guess their roles. The description adds only minimal meaning over the bare parameter names.

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 states a specific verb and resource: 'Technical SEO audit of a URL' with a concrete list of deliverables (title/meta review, heading structure, indexing/sitemap observations, prioritized recommendations). This clearly distinguishes it from other SEO tools like content briefs or page generators, even without naming siblings.

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?

No guidance is given on when to use this tool instead of other SEO-related siblings (e.g., seo_content_brief, seo_page_generator). There are no exclusions, prerequisites, or alternative scenarios mentioned. With over 100 sibling tools, this omission is significant.

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