Keyword clustering

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

The description discloses that the operation may consume SEO Intellect account limits, which is a meaningful operational trait not captured by the annotations. However, it does not mention the asynchronous behavior visible in the schema, such as returning a task_id or polling, which limits full transparency.

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 short and front-loaded with the core purpose. The phrase 'Upstream API tool: clustering' is somewhat redundant with the tool's name and adds little value, but the overall structure is efficient.

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 has a complex anyOf schema with two modes (starting a clustering task and continuing with a task_id) and async polling parameters, but the description does not explain these modes or what the tool returns. With no output schema, the description should provide more operational context to be complete.

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%, so the schema already documents the parameters and their meanings. The description does not add parameter-level semantics, but the baseline of 3 applies because the schema carries the full burden.

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 states a specific verb ('Cluster'), a resource ('a semantic core'), and the method ('using search-result overlap'). This clearly distinguishes it from the sibling tools, none of which target clustering.

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 implies the tool is used for clustering keywords by search-result overlap, but it does not explicitly state when to use it versus alternatives or when not to use it. The 'may consume account limits' warning hints at cost-conscious usage but provides no exclusion criteria.

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