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

Annotations mark this as a non-read-only, open-world, non-idempotent job. The description adds genuinely useful behavior beyond that: it returns a handle immediately (async pattern), and warns that themes are synthesized and quotes must be verified before publishing. No destructive/auth details, but the async and reliability caveats are valuable.

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 load-bearing — purpose, inputs, options, return/next step. Front-loaded with the action and no filler; the verification caveat is well placed at the end.

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?

With no output schema, the description compensates by naming the returned job handle and downstream fields (themes, featureGaps, positioningHooks) available via get_job. Adequate for an async job tool, though job lifecycle/failure behavior is not covered.

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 baseline is 3, but the description adds real meaning: it clarifies corpus should hold pasted G2/Capterra/Trustpilot reviews because those sites aren't fetched, and frames focus as an optional theme filter. This resolves the corpus-vs-reviewUrls decision beyond the schema text.

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?

States a specific verb and resource — 'Start a review VOC-pack job' — then names the exact output (pain themes with cited quotes). This is clearly distinguishable from siblings like get_job or news_analyzer.

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?

Explains the operating context: pass reviewUrls and/or corpus, aggregator sites are never fetched so their reviews must be pasted, and results are retrieved later via get_job. Lacks an explicit when-not-to-use statement against alternatives, but the workflow routing is clear.

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