wait_for_otp

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

No annotations provided, but description fully discloses blocking nature, polling mechanism, return values, and error handling. Mentions auto_reroute behavior on timeout, adding transparency beyond expected defaults.

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?

Five sentences, each with a distinct purpose: behavior, polling, return value, error handling, post-use instruction. No redundant or irrelevant information.

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?

Complete for a tool that waits for an OTP: covers blocking, timeout, retry, auto-reroute, and post-step. Output schema exists, so return values are documented elsewhere.

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 has 0% coverage (no param descriptions in description), but schema itself includes descriptions for all parameters. The description adds context by linking timeout_seconds to polling time and auto_reroute to retry logic, providing value beyond the schema alone.

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 the tool blocks until an OTP arrives, polls the API, and returns the code and message. The verb 'wait' and resource 'OTP' are specific, and it distinguishes itself from siblings like release_number by mentioning post-use actions.

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 advises to call release_number after OTP use, and describes behavior on timeout (raises ToolError with retry advice). Includes auto_reroute option, providing clear when-to-use and post-condition steps.

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