audit_page_seo

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

There are no annotations, so the description carries the full burden of disclosing behavior. It only restates the tool's name without explaining what the audit does, what data it examines, what it returns, or any side effects. This is essentially missing behavioral transparency.

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 only four words, which is concise, but it is under-specified rather than effectively concise. It lacks enough content for the agent to use the tool correctly, so the brevity is a deficiency rather than a strength.

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 tool with no annotations, no output schema, and only minimal parameter names, the description is completely inadequate. It does not provide necessary context about the audit scope, return value, or how to interpret results, making it impossible to use correctly without additional information.

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?

The input schema has two parameters (taskId, pathname) with 0% description coverage. The description does not explain what 'taskId' or 'pathname' mean in context, nor how they affect the audit. The agent must rely solely on the parameter names, which are insufficient.

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 ('Audit') and resource ('page SEO'), indicating the tool audits SEO for a page. However, it is vague about what aspects of SEO are covered, and given sibling tools like audit_heading_structure, audit_internal_links, and audit_structured_data, it does not distinguish itself clearly.

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 provided on when to use this tool versus the many alternative audit tools. There is no mention of prerequisites, intended scenarios, or exclusions, leaving the agent to guess when this tool is appropriate.

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