seo_agent

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

Lists API key requirement and credit consumption, but does not disclose if actions are read-only or modify data. No annotations to compensate.

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?

Concise at 4 sentences, front-loads main purpose. Could benefit from bullet points for agents.

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?

Covers API key, credits, auto-detection, and project enrichment. Lacks details on agent behaviors and output, though output schema exists.

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 coverage is 0%, but description explains several parameters (task, agent, project_id) and their roles. Does not fully explain 'params' or 'content'.

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?

Clearly states it runs a specialized SEO agent and lists available agent types (crawling, seo_analyst, etc.). Suggests differentiation from sibling tools but does not explicitly contrast.

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?

Mentions enriching with project context and checking balance via get_account_info, but no explicit when-to-use or when-not-to-use. Implies general orchestration tool.

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