seo_meta_analyze

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

With no annotations provided, the description carries the full burden. It discloses that the tool returns SEO issues and recommendations, implying a read-only analysis. However, it does not mention whether it performs a live fetch, whether page accessibility affects results, or any authentication/rate-limit considerations.

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 concise and front-loaded with the core action, then lists the relevant tag types and states the return value. Every sentence earns its place, with no filler or redundant phrasing.

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 one-parameter tool, the input side is complete. However, there is no output schema and the return value is only generically described as 'SEO issues and recommendations' without any structure or detail. An agent can select the tool confidently but may not know exactly what shape the response will take.

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% for the single 'url' parameter, and the description adds no additional semantic details about URL format, requirements, or constraints. The schema already explains the parameter adequately, so the baseline of 3 applies.

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 identifies a specific verb ('Analyze') and resource ('page meta tags'), enumerating tag types like title, description, Open Graph, Twitter Cards, robots, and canonical. It does not explicitly differentiate itself from overlapping siblings such as seo_canonical_check or seo_robots_analyze, but the overall scope is clear enough.

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 gives no guidance on when to use this tool versus related SEO siblings like seo_canonical_check, seo_robots_analyze, or seo_sitemap_analyze. It implies use for meta tag analysis but provides no exclusions or alternative routing.

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