wait_for_reply

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

The description transparently outlines smart polling intervals and behavior for different elapsed times. However, it does not mention potential side effects, error handling, or authentication requirements, leaving minor gaps.

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 well-structured, concise, and front-loaded with the main purpose. Every sentence adds value, using bullet points and a clear table for parameter guidance.

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, output schema present), the description is sufficiently complete, covering behavior, parameter selection, and usage context without unnecessary details.

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 single parameter max_wait_seconds is thoroughly explained with a default, a description of its purpose, and a table of recommended values for various contexts, compensating for the 0% schema description coverage.

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 tool waits for a user reply via Telegram and returns it, distinguishing it from sibling tools that send messages. It specifies handling of both text and callback queries.

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 explicit guidelines for when to use the tool, including a detailed table mapping scenarios to recommended max_wait_seconds values, helping the agent select appropriate parameters.

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