seo_create_cluster

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

With no annotations provided, the description carries full burden. It discloses key behaviors: bypasses auto-clustering (no LLM call), starts empty, tagged with origin 'manual', created as 'approved', and returns a clear error on duplicate names. This is comprehensive and goes beyond a simple 'creates a cluster'.

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, but each part earns its place: what it does, how it differs, the workflow, the tagging/approval behavior, and error handling. It's structured logically and not overly verbose for the complexity.

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's complexity, lack of annotations, and no output schema, the description provides a complete picture: purpose, lifecycle, error handling, and relationship to sibling tools. Enough for an agent to use it correctly without extra information.

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 100%, so the baseline is 3. The description doesn't add significant parameter-specific meaning beyond what the schema already provides. It mentions name uniqueness and returned id, but the schema already documents name as unique and the workflow is explained rather than adding new parameter semantics.

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 tool's function: 'Create a real, named SEO cluster by hand' and distinguishes it from the auto-clustering pipeline. It specifies the resource (SEO cluster), the verb (create), and the method (manual), setting it apart from sibling tools like seo_generate_clusters.

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?

Explicitly explains when to use this tool (manual cluster creation) and what to do next (use seo_create_custom_brief with returned id). It also provides alternatives when a name is already taken, directing to seo_list_clusters, and names the auto-pipeline it bypasses.

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