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

With no annotations provided, the description carries the behavioral disclosure burden. It clearly explains the blocking behavior, timeout handling, and the timed_out:true return instead of an error. This goes beyond the schema and gives the agent important expectations about how the tool behaves.

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 compact and front-loaded with the core behavior, then the ideal flow, then the timeout edge case. Every sentence contributes meaningful information without redundancy or filler.

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 no output schema, the description explains the key return behavior (full capture or timed_out:true) and timeout semantics. It could say a bit more about error conditions or the exact shape of the returned request, but the essential invocation context is 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 description coverage is 100%, so the parameters are already well documented. The description adds a useful paraphrase about after_id (waiting for the next capture after 'now'), but it does not materially expand on the schema's parameter documentation.

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 states a specific action (block until next request arrives) on a specific resource (a bin) and clarifies the return behavior. It clearly distinguishes this tool from siblings like get_capture and list_captures, which retrieve existing data rather than waiting for new data.

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 an explicit ideal flow: create_bin → configure webhook sender → trigger it → wait_for_capture, which gives clear operational context. It does not explicitly name alternative tools or state when not to use this one, but the intended sequence is clear enough for an agent.

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