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

With no annotations provided, the description carries the full behavioral disclosure burden. It conveys that the tool returns a list of operational alerts and explicitly promises no PII, which gives some safety-relevant context, but it does not mention response structure, pagination, authorization, or whether alerts are cached.

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 with no filler. Every word contributes to understanding the purpose and a key constraint (no PII).

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 tool has only one parameter and no output schema, so the description is the only source for return-value context. 'List current operational alerts' does communicate the general result shape, but alert severity, timestamps, and whether any pagination or limits apply are left unspecified.

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 100%, so the single `organization_id` parameter is already documented in the schema as 'Active organization ID'. The description adds no additional parameter-level meaning, and the baseline of 3 applies because the schema handles the documentation burden.

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 a specific verb ('List') and resource ('current operational alerts'), making the tool's function immediately clear. It also differentiates itself from the sibling `commsharbor_operations_refresh` by describing a read/list operation rather than a refresh operation.

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?

No guidance is given about when to use this tool versus alternatives like `commsharbor_operations_refresh`, `commsharbor_health`, or `commsharbor_audit`. The word 'current' implies a status check, but there is no explicit context, prerequisite, or exclusion.

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