Start Keyword Expansion

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

The description adds 'asynchronous' and 'breadth-first/round-based' which clarify behavior beyond annotations. However, it does not disclose whether the process is cancellable, how long it takes, or that it returns an expansion ID. With annotations already covering read/write hints, this is a moderate addition.

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 sentence that is concise and front-loaded with the key characteristic 'asynchronous'. It is efficient but could include a bit more detail without losing conciseness.

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 that this is an asynchronous tool with 7 parameters, the description is incomplete. It does not mention the return value (likely an expansion ID), how to check status, or any caveats about the asynchronous process. Although an output schema exists, the agent still needs to know what to expect. Score is low.

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 schema already describes all 7 parameters with descriptive names and brief descriptions. The tool description does not add any additional context or examples for parameters like include_rules or exclude_rules. Score is baseline 3 as schema coverage is 100%.

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 that the tool starts an asynchronous breadth-first/round-based keyword expansion, which distinguishes it from synchronous sibling tools. However, it does not mention the return value or how to obtain results.

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 siblings such as get_related_keywords or discover_keywords. The description lacks context for selection.

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