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

With no annotations, the description carries the full behavioral burden and does not say what happens after a pick is submitted, whether the choice is final, what output to expect, or any side effects. It discloses only the trigger and two inputs, leaving the mutation/interaction semantics opaque.

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?

It is very compact and front-loads the trigger condition with no filler. But it reads as a cryptic fragment with unexplained status terms and parentheses, so it is concise at the expense of structural 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?

For a four-parameter clarification tool with no annotations and no output schema, the description is too sparse. It omits the meaning and effect of the optional parameters, the expected result of submitting a pick, and any behavioral constraints an agent would need to call it safely.

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 only 50%. The description mentions 'session_id' and 'pick', but those are already described in the schema, while the optional 'format' and 'include_payload' parameters remain unexplained in both places. The description therefore does not compensate for the coverage gap.

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 identifies a clarification step after an 'ambiguous' or 'need_clarification' state, plus the required inputs 'session_id' and 'pick'. However, it never states in plain terms that the tool selects a candidate or resolves ambiguity, so the core action remains only inferable from the schema's 'pick' description.

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?

It clearly states the trigger conditions: use after an ambiguous company result or a need_clarification segment result, and pass session_id plus pick. It stops short of naming alternatives or when not to use it, but the context for invocation is unusually explicit for a short description.

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