aeo_seo_research_generate_research_action

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

No annotations provided, so description carries full burden. It mentions generating research and lists included aspects, but does not disclose side effects, auth requirements, or output structure. Adequate but not rich.

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?

Single sentence that is front-loaded with the purpose and includes a list of outputs. No wasted words.

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 5 parameters, low schema coverage, no output schema, and no annotations, the description lacks guidance on parameter usage, output format, and when to use sibling tools. Insufficient for a complex research tool.

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 only 20% (output_variable_name has a description). The description does not explain any parameters beyond the topic, leaving research_depth, website_url, and optimization_focus unexplained. Fails to compensate for low schema coverage.

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?

Description clearly states it generates comprehensive AEO & SEO research for a topic, listing inclusions like keyword opportunities and competitor landscape. It distinguishes from siblings like industry_research_generate_research_action by specifying AEO & SEO focus.

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?

Implied usage for AEO & SEO research tasks, but no explicit when-to-use or when-not-to-use guidance. No alternatives are mentioned despite sibling tools with similar names.

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