bourne_execution_wait

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

Annotations already convey non-read-only, non-idempotent, non-destructive. The description adds that waiting creates no execution, which is a useful behavioral note, but it does not disclose error behavior, timeout side effects, or what happens if execution is missing. It adds marginal value beyond annotations.

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?

Two clauses, concise, front-loaded with the primary action. Every word contributes meaning without repetition.

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?

An output schema exists, so return values are covered. However, for a wait tool, the description lacks parameter explanations and usage context, leaving the agent to infer 'reference' and timeout semantics. It is adequate but has clear gaps.

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?

With 0% schema description coverage, the description carries the burden. It hints at the optional timeout via 'optional bounded caller timeout', but does not explain what 'reference' refers to or how to format it. The description does not fully compensate for the schema 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 clearly states the verb 'wait' and the resource 'existing Bourne-managed scheduled execution', and explicitly notes it creates no execution, distinguishing it from creation tools. It is specific and unambiguous, though it doesn't name sibling alternatives.

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 implies use when you need to block on an execution, but provides no explicit when-to-use vs alternatives like bourne_execution_get or bourne_execution_cancel. No mention of when not to use or prerequisites such as initiating an execution first.

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