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

No annotations are present, so the description carries the full behavioral burden. It discloses the blocking long-poll behavior, the default timeout (25 seconds), and the security stance that peer text is untrusted. It does not say what happens on timeout or whether messages are consumed, so it falls short of a 5.

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?

Three short sentences, front-loaded with the core behavior, followed by exclusion guidance and a security warning. Every sentence earns its place, with no redundancy or filler.

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?

The description covers purpose and usage well, but with no output schema and no annotations it leaves out return behavior and timeout/edge-case handling. For a long-polling tool, that is a notable gap, though an agent can still invoke it correctly with defaults.

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%, and the description only mentions 'default 25 seconds', which merely duplicates the wait_seconds default already in the schema. It does not explain limit or token, nor how the parameters affect polling behavior, leaving a significant gap for an agent choosing values.

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 verb and resource: 'Long-poll the inbox until mail arrives' and gives concrete trigger cases ('missed mail, connect_requests, and after timed_out'). It does not explicitly name a sibling like check_inbox, so it doesn't fully differentiate from alternatives, but the operation itself is clear.

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?

It explicitly tells the agent when to skip ('when the turn already started from a webhook body') and when to use it ('missed mail, connect_requests, and after timed_out'). This is direct when/when-not guidance, which is exactly what an agent needs for selection.

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