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

The description discloses that the tool takes approximately 30-60 seconds, which informs the user about latency. It also lists the expected outputs (debate, contradiction map, synthesized briefing). There are no annotations, so the description carries the burden. It does not mention any failure modes or side effects, but for a content-generation tool, this level of transparency is adequate.

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 concise, using only two sentences to convey the purpose, optional parameters, and expected outputs. It is well-structured and avoids unnecessary detail, making it easy for an agent to parse quickly.

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 description provides sufficient context for using the tool: what it does, what it returns, and the optional parameters. It does not define 'contradiction map' or detail the output format, but the schema covers parameter types and the overall purpose is clear. The context is complete enough for an agent to decide to invoke it.

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?

The schema already describes both parameters (topic and personas), and the description adds the important clarification that omitting personas auto-selects a fitting panel. This directly enhances the understanding of the optional parameter, making the semantics fully clear.

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 purpose: to convene a panel of expert personas to debate a topic and return specific outputs (debate, contradiction map, synthesized briefing). This distinctly differentiates it from the sibling tool list_personas, which is for listing available personas, not running debates.

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 provides practical guidance on when to use it, mentioning that persona ids are optional and can be obtained via list_personas, and that omitting them auto-selects a panel. It does not explicitly state 'use this when you need a debate' but the purpose is self-evident and the reference to list_personas gives a hint for the workflow.

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