wait_for_otp

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

The description communicates that the tool polls or blocks until an OTP arrives or a timeout occurs, and it gives the return shape. With no annotations available, this carries more weight; however, it leaves the timeout failure behavior unspecified and does not clarify whether the OTP email is merely read or consumed.

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 two short sentences with no filler. It front-loads the core polling action and then states the return format, leaving no wasted words.

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 low-complexity tool, the description is minimally sufficient: it states when to call it, what happens, and what it returns. But because there are no annotations, no output schema, and no parameter descriptions, the inability to describe the address and timeout failure behavior is a notable gap.

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 descriptions the required address parameter are not explained, nor is the timeout parameter's unit or exact behavior. The description only mentions 'timeout' loosely without adding what an agent needs to fill the required field correctly.

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 operation — polling the inbox until an OTP code arrives — and specifies the returned payload. It clearly distinguishes itself from generic sibling tools like wait_for_message through its OTP-specific behavior.

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 intended context is implied: use this when expecting an OTP in an inbox. However, the description does not explicitly state when to prefer this over wait_for_message or how it relates to read_messages, so guidance is only implied rather than explicit.

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