audit_seo_metadata

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

No annotations are provided, so the description must disclose behavior fully. It clarifies the tool is 'fast' and 'offline' but does not explicitly state that it is read-only (no mutations), nor does it mention assumptions about HTML well-formedness or limitations. The list of audited items is helpful, but additional behavioral context is missing.

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, clear sentence with no unnecessary words. It front-loads the purpose and enumerates key audit categories efficiently. Every word contributes value.

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?

Given the tool's simplicity (one parameter, no output schema) and the context provided by sibling tools, the description is largely complete. It mentions the offline nature and the scope of checks. However, it could improve by hinting at the output format (e.g., a report or score) or clarifying that it does not fetch external resources.

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 one parameter (htmlContent) with 100% schema description coverage. The description adds no extra meaning beyond what the schema already provides; it merely restates that the HTML content is analyzed. Without additional parameter semantics, a baseline score of 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 clearly specifies the tool's function: auditing SEO metadata including HTML metadata, heading structure, viewport tags, image alt tags, and Open Graph cards. It uses a specific verb (audits) and resource (HTML metadata), and its focus on SEO distinguishes it from sibling tools like check_broken_links or validate_schema_markup.

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 mentions 'fast offline audit', implying usage context (quick checks before publishing) but does not explicitly state when to use this tool versus alternatives like validate_local_html or validate_schema_markup. No exclusion criteria or when-not-to-use guidance is provided.

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