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

There are no annotations, so the description carries full weight. It discloses the specific status data returned (accounts watched, connection status, email counts), which is useful. However, it does not mention whether a watch must be active, how connection status is represented, or that the operation is read-only, though 'Get' implies non-mutating behavior.

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?

A single, front-loaded sentence states the verb and resource first, then enumerates the key returned data. No filler or repetition.

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?

Without an output schema, the description adequately outlines return values (watched accounts, connection status, email counts). It could be more exhaustive about error conditions or empty states, but for a no-parameter status endpoint it provides the essential information.

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 tool has zero parameters, so schema coverage is trivially 100%. According to the rubric, a baseline of 4 applies, and the description correctly omits parameter details since none exist.

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 uses the specific verb 'Get' and clearly identifies the resource as 'status of IMAP IDLE watchers', listing concrete output types (accounts being watched, connection status, new email counts). This distinguishes it from sibling status tools like get_health_status or get_smtp_receiver_status.

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?

While no explicit alternatives are mentioned, the description's focus on IMAP IDLE watchers gives clear usage context: use it to monitor active IDLE watching sessions. It does not exclude related tools, but the resource specificity makes the intended use obvious.

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