gdb_wait

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

Discloses it polls until target stops and returns the stop reason, but does not clarify behavior on timeout (e.g., returns an error or times out gracefully). No annotations exist, so description holds full burden; lacks completeness about blocking nature and side effects.

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 sentences front-load the key information: purpose and return value. No redundant text.

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 simplicity (one optional parameter, no output schema), the description covers essential aspects: what it does, when to use it, and what it returns. Minor gap: no mention of timeout behavior, but overall sufficient for selection.

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 description does not elaborate on the 'timeout' parameter beyond what the schema already states (how long to wait). With 100% schema coverage, baseline is 3; no additional value provided.

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?

Clearly states it polls for target stop after a continue/step that timed out, distinguishing it from sibling tools like 'step' or 'halt'. Specifically identifies the verb (poll), resource (target stop), and condition (after timeout).

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?

Explicitly says 'after a continue/step that timed out', providing clear context for when to use. Does not mention alternatives or exclusions, but the context is sufficient for typical use.

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