aeo_cluster_prompts

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

The readOnlyHint annotation already establishes this is a safe read operation. The description adds value by mentioning text embedding similarity and the return shape, but does not disclose potential caveats such as input size limits, API costs, or how 'clusters' are represented.

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 two sentences, front-loaded with the core purpose, then provides compact input and output contracts. No wasted words; every sentence contributes meaningful information.

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 the tool has no output schema, the description does mention return keys ({clusters, n_items, n_clusters}) but does not describe the structure of each cluster. It also omits semantics for three optional parameters. It is adequate for a simple clustering operation but leaves meaningful gaps.

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 0%, so the description must compensate. It does explain the structure of 'items' with id/text/intent?/volume?, which is helpful, but leaves 'brand', 'config', and 'distance_threshold' undocumented. The distance_threshold parameter is especially important and receives no explanation.

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 verb ('Group'), the resource ('prompts'), and the method ('by text embedding similarity'). It distinguishes from sibling tools such as aeo_cluster_by_urls by explicitly targeting prompts rather than URLs.

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 usage context is implied: use this tool when you need to cluster prompts by topic. However, there is no explicit guidance on when to use this over alternatives like aeo_filter_prompts or aeo_cluster_by_urls, and no exclusion criteria.

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