Start Until Unanimous

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

Minimal behavioral disclosure: mentions background execution and termination conditions. Does not discuss side effects, cost, permissions, or how to handle results. Annotations indicate mutating and non-idempotent, but description adds little beyond.

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?

Very concise, two sentences. Front-loaded with primary function. However, conciseness comes at the cost of completeness; a bit more length could improve clarity.

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 (14 parameters, many siblings, no output schema), the description is insufficient. Lacks explanation of parameter roles, usage flow, and how to monitor or interact with the started session.

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?

Description provides no parameter explanations. Schema description coverage is very low (14%), and the description does not compensate. Critical parameters like task, mode, peers, caller, etc., are left undocumented.

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 the action clearly: start rounds in background until unanimity/limit. However, it relies on referencing run_until_unanimous for specific semantics, and does not fully distinguish from siblings like session_start_round.

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?

No explicit guidance on when to use this tool vs alternatives. Merely references run_until_unanimous for details, leaving the agent to infer usage context.

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