seo_analyze

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

Annotations are absent, so the description carries full responsibility for disclosing behavior. It only says 'analyze,' implying a read-only operation, but doesn't confirm whether it makes external requests, requires authentication, or returns a specific report structure. This leaves room for uncertainty about side effects and output.

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 sentence exactly states the purpose without any filler. All words contribute meaning.

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 tool takes a URL and optional keywords but provides no output schema or description of what the analysis returns. The description doesn't elaborate on the scope of SEO issues covered, the format of results, or any limitations. For an analysis tool, this is a significant gap.

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?

Both parameters are described in the schema (url and keywords), covering 100% of parameters. The description does not add details about parameter formats, defaults, or how keywords influence analysis. However, the schema descriptions are sufficient for basic use.

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 states the tool analyzes a page for SEO issues and opportunities, using a specific verb and resource. While it doesn't explicitly distinguish from sibling tools, 'SEO' narrows the scope. However, it lacks explicit differentiation from potential overlapping tools like insights_analyze.

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 alternatives. The description only states the action, with no mention of prerequisites, exclusions, or alternative tools. Agents must infer usage from the tool name alone.

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