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

With no annotations, the description must carry behavioral disclosure. It explicitly guarantees no recipient PII ('never with recipient PII') and lists the alert categories, which is useful. However, it doesn't explicitly confirm read-only behavior, mention response format, time-sensitivity, error conditions, or rate limits. 'List' implies a read operation, but more explicit transparency about expected behavior would be better.

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 a single, front-loaded sentence that begins with the core action and scope, then enumerates the alert categories. While the list is somewhat long, each item adds specificity and helps set expectations. There is minimal redundancy, and the no-PII guarantee is placed at the end for emphasis.

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?

For a simple one-parameter list tool, the description provides the core purpose, scope, and privacy constraint. However, with no output schema, it does not specify the structure of the returned alerts (e.g., list of objects, counts, status flags) or any pagination behavior. This leaves some uncertainty about how to interpret the tool's response, though the described categories offer a reasonable expectation.

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 schema description coverage is 100%: the only parameter, organization_id, is described as 'Active organization ID'. The tool description adds no additional information about parameters or their usage. Per the baseline rule for high schema coverage, this is acceptable, and the description doesn't need to compensate for any gaps.

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: 'List current operational alerts' with scope 'without PII' and a detailed list of covered categories (dead letters, backlog, worker and SNS failures, reputation, etc.). It distinguishes itself from sibling tools like commsharbor_dead_letters or commsharbor_health by presenting a consolidated operational alert overview, though it doesn't explicitly name these alternatives.

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?

The description provides clear context about what the tool does and what alerts it covers (dead letters, backlog, statuses, quotas), but it doesn't explicitly state when to use this tool versus alternatives such as commsharbor_health or commsharbor_operations_refresh. No when-not-to-use guidance or alternative routing is given, leaving usage inference to the agent.

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