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

With no annotations, the description carries the full behavioral burden. It hints that any mailbox name works without setup ('is live') and that extraction is deterministic, but a tool named 'poll' says nothing about polling semantics: whether it blocks, retries, waits for a message, times out, or what happens when no message has arrived. No rate limits, auth, or message lifetime information either.

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 short sentences with the core capability front-loaded and no padding. It is efficiently sized, though the marketing phrasing ('zero-friction') costs a little precision against the space it occupies.

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?

No output schema and no annotations mean the description must explain behavior and results, but it omits polling behavior, timing, and failure modes for a tool whose name promises polling. One of two parameters is undocumented. For an OTP-retrieval tool this is materially incomplete.

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 description coverage is 0%, so the description must compensate. It loosely maps 'mailbox name is live' to inbox_prefix but gives no format, constraints, or determinism rule, and x_session_purpose is entirely unexplained in both schema and description. A quarter of the parameters are effectively undefined.

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 conveys an inbox that accepts any mailbox name and returns stored messages plus extracted OTPs/links, but the framing is marketing-flavored ('zero-friction') rather than stating the verb+resource directly. It never explicitly says it creates/provisions a mailbox or what 'poll' means, despite the name. Purpose is inferable but not crisply stated.

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?

There is no statement of when to use this versus alternatives, no prerequisites, and no exclusions. The siblings (persist_memo, schedule_wakeup, webhook_echo) are unrelated, so cross-routing matters less, but the agent still gets no cue about when this tool is the right choice for OTP retrieval.

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