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

The description discloses several behaviors beyond annotations: deterministic rules, no AI call, deliberate bias toward BLUE, per-verdict rule attribution, and cost of 1 MESH/call. However, given readOnlyHint=false, it does not explicitly address whether the tool has any side effects, which is a minor omission.

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 dense but well-structured, front-loading the core question and then covering rules, bias, input, output, and cost. Every sentence contributes information without redundancy.

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 is present, but the description explicitly provides the return shape ({lane, waiting, rule, summary}), which is sufficient. It also covers logical behavior, input options, and guarantees such as not inventing a waiting customer.

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 input schema already provides detailed descriptions for all properties, giving 100% coverage, so the baseline is 3. The description adds value by clarifying the two input modes—structured fields or a whole raw email via 'message'—which helps the agent choose the correct format.

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's function: to triage emails and answer whether a human is waiting for a reply. It uses a specific verb (triage) and resource (mail), and distinguishes itself from siblings by emphasizing deterministic rules and no AI call.

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 provides clear context about when to use it—when a busy owner needs to know if an actual person is awaiting a response. However, it does not explicitly mention alternatives or when not to use it, so it lacks the explicit exclusions required for a 5.

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