seo_audit_meta

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

With no annotations provided, the description carries the full burden of behavioral disclosure. 'Audit' suggests a read-only operation, but there is no explicit statement about side effects, authentication requirements, or output format. The description adds little beyond the verb itself.

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?

One focused sentence with no filler. The verb appears first and the scope is compactly enumerated. Every word contributes to the purpose.

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 adequate for basic selection and invocation, covering the main purpose and leaving parameter details to the schema. However, there is no output schema and no indication of what the audit result looks like, which is a meaningful gap for an analysis tool.

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 100%, so the schema already explains url, html, and api_key. The description does not add parameter-specific detail, but the baseline of 3 is appropriate because structured fields carry the semantic weight.

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?

Description states a specific verb ('Audit') and concrete resources (HTML meta tags, Open Graph, structured data), plus the outcome ('SEO completeness'). This clearly distinguishes it from similarly named siblings like seo_audit_performance by focusing on metadata structure rather than performance.

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 this tool is for auditing metadata/SEO completeness, but it does not explicitly state when to prefer it over alternatives such as seo_audit_performance or seo_generate_fixes, nor does it mention any exclusions. Usage context is only inferred from the wording.

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