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

Annotations already declare readOnlyHint=true, openWorldHint=false and destructiveHint=false, so the safety profile is covered. The description adds real domain context by naming the two settings that can block messages, but says nothing about aggregation behavior, whether results are per-brand, or how the count is scoped.

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 compact sentence with no filler. The interrogative phrasing is slightly indirect for a tool definition, but nothing is wasted.

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?

There is no output schema, so the description carries the burden of explaining return values — and it only loosely implies a numeric count. It's unclear whether the response is one number, a per-brand breakdown, or a list of affected customers, which is a meaningful gap for an agent deciding how to present results.

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 coverage is 100% and the single `brand` parameter is fully documented in-schema, including the get_overview `brands[].slug` sourcing hint and the omit-when-single-business rule. The description adds nothing about the parameter, so baseline 3 applies.

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 frames the tool as a question ('How many customers have a message waiting…') rather than stating a verb+resource, and it never says outright that it returns a count. It does convey the specific condition being checked (unset signup link or review link), which distinguishes it from list_needs_you and update_settings, but the agent must infer the operation and output shape.

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 explicit guidance on when to call this instead of a sibling such as get_overview, get_my_standing, or update_settings. The 'setup status' framing only implies a diagnostic context; no exclusions or alternatives are named.

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