seo_approve_cluster

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

With no annotations, the description fully discloses side effects: it gates brief generation, kicks off an async job, returns an operationId, and instructs polling get_job with specific terminal states. It also notes timing (~2-5 min). This is thorough behavioral disclosure.

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?

Four sentences, each earning its place: action, flow position, timing, and return/polling behavior. Front-loaded with the primary action, 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?

No output schema, but the description explains the return shape and async workflow completely. It covers prerequisites (via flow position) and error handling via polling states, making it sufficient for a tool with this complexity.

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% with descriptions for both params. The description adds little beyond schema, though it reinforces that clusterId comes from seo_list_clusters (already in schema). Baseline 3 applies because schema does the heavy lifting.

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 opens with 'Approve a single cluster,' which is a specific verb and resource that clearly states the action. It distinguishes from siblings by emphasizing 'single' (vs. bulk) and clarifying its role as a gate for brief generation.

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?

Provides explicit flow position: 'after seo_generate_clusters + seo_list_clusters, before seo_generate_roadmap / brief review.' This tells the agent when to call it. It does not explicitly name alternatives like seo_bulk_approve_clusters, but the 'single cluster' wording implies the distinction.

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