neuron_seo_audit

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. It does state the return behavior ('Returns findings with severity levels'), which is useful, and 'audit' implies a read-only operation. However, it never explicitly says the tool does not modify the page, does not mention permissions or auth needs, and gives no details on edge cases like unloaded tabs or missing elements.

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 a single, information-dense sentence with zero filler. It front-loads the core purpose ('SEO audit of a page') and then efficiently lists the full scope of checks before closing with the output behavior. Every item in the list earns its place by informing the agent what the audit covers.

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-parameter tool with no output schema and no annotations, the description is reasonably complete: it enumerates all audited elements and states that findings carry severity levels. It falls short of full completeness by not describing the result structure in more detail or noting any prerequisites or failure modes, but the core information an agent needs to invoke and interpret the tool is present.

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%: the only parameter, tabId, is already documented as 'Chrome tab ID'. The description adds no extra meaning about this parameter beyond 'of a page', which only loosely connects the tab to the audit target. Since the schema fully handles the parameter semantics, a baseline 3 is appropriate.

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 opens with 'SEO audit of a page', a specific verb plus resource, and then enumerates concrete audit dimensions (title, meta description, Open Graph, Twitter Cards, canonical URL, headings, alt text, structured data, etc.). This clearly distinguishes it from sibling tools like neuron_a11y_audit, neuron_security_scan, and neuron_perf_snapshot, so an agent can select it correctly without opening any 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?

There is no guidance on when to use this tool versus alternatives such as neuron_audit_page or neuron_a11y_audit. The description implies 'use for SEO audits' but provides no exclusions, prerequisites (e.g., page must be loaded), or conditions for choosing a different audit tool. No explicit when/when-not guidance is present.

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