wait_for_device

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

Given no annotations, the description discloses blocking behavior and timeout. It could mention whether the operation is safe or idempotent, but the basic behavioral traits are covered.

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 plus an argument list, front-loaded with purpose. Every word adds value with no redundancy.

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 simple tool with one parameter and an output schema, the description covers behavior, usage, and parameters completely. No additional information needed.

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 explains the timeout parameter as 'Max seconds to wait (default: 30)', adding meaning beyond the schema's default value. With 0% schema coverage, the description compensates well.

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 ('device to pair after scanning the QR code'). It also distinguishes from siblings by specifying the blocking behavior until a device joins the editing channel, which is unique among the listed sibling tools.

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 clear context: use after scanning QR code. It does not explicitly list alternatives or when not to use, but the context is sufficient for a simple wait operation.

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