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

No annotations are provided, so the description must disclose behavioral traits. While it mentions long polling and a 60s timeout, it omits critical details like what happens on timeout (returns null/error?), whether the operation is cancellable, and if it consumes messages or leaves them intact.

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 a single, front-loaded sentence that efficiently conveys the core function. However, it omits enough detail that the conciseness comes at the cost of completeness.

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 no annotations, no output schema, and four undocumented parameters, the description is far from complete. An agent lacks critical information about return values, error handling, and proper parameter usage to invoke this tool correctly without external knowledge.

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?

With 0% schema description coverage, the description adds no meaning to the four parameters. Key aspects like default timeout (30s vs the noted 60s max), filtering semantics (fromContains, subjectContains), and the required mailboxId's format or source are left entirely to the agent to infer from schema names 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?

The description clearly states the action ('Wait') and resource ('incoming message') with an important qualifier ('long polling, max 60s'). It implies a blocking operation distinct from sibling tools like agent_tempmail_list or agent_tempmail_get, which are likely immediate/retrieval operations.

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?

No guidance is given on when to use this tool versus other tempmail operations or alternatives. The agent receives no context about prerequisites, polling strategies, or whether to prefer synchronous waiting vs manual polling.

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