callback_wait

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

With no annotations provided, the description carries the full burden of behavioral disclosure, but it only says 'Wait for callback' with no information about whether the tool blocks, how it handles timeouts, what the 'timeout' parameter does, or what happens when a callback is received. This is entirely inadequate for an operation that likely has side effects or blocking semantics.

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 extremely concise but under-specified. While it is front-loaded with the verb 'wait', it omits necessary detail and thus fails to be appropriately sized for the tool's complexity. The three-word sentence does not earn its place because it conveys no more than the tool name.

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 2-parameter schema, no annotations, no output schema, and a large set of sibling callback tools, the description is grossly incomplete. It lacks any information about return values, side effects, or how it differs from similar tools, making it nearly impossible for an agent to select and invoke this tool correctly without additional context.

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 lists two parameters (timeout and protocol) with no descriptions, and the schema description coverage is 0%. The tool description does not mention either parameter, providing no additional meaning about their units, valid values, or purpose. For example, it is unclear if timeout is in seconds or milliseconds, and what protocol refers to.

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 'Wait for callback' is essentially a tautology of the tool name 'callback_wait', restating the action without providing additional context. It does not clarify what kind of callback, how long to wait, or what triggers it, so it falls short of a clear purpose statement.

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?

There is no guidance on when to use this tool versus its siblings such as callback_check, callback_status, or callback_latest. The description offers no context about typical use cases, prerequisites, or alternatives, leaving the agent to infer the tool's role among a large family of callback-related tools.

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