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

The annotations already disclose readOnlyHint=true and idempotentHint=true, so the safety profile is known. The description adds the group-membership authorization requirement, which is useful context beyond annotations, but it does not disclose pagination behavior or what the listing returns.

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?

Two short sentences with no waste. The core listing purpose is front-loaded, followed immediately by the key authorization constraint.

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 read-only listing tool with annotations covering safety and a schema documenting most parameters, the description supplies the essential purpose and group-membership prerequisite. The only material gap is the undocumented offset parameter, which is minor for this tool's complexity.

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 75%, with group, limit, and state documented in the schema, while offset is left blank. The description only reinforces the group parameter's scope and adds no syntax or default details beyond the schema, so it meets the baseline for mostly schema-documented parameters.

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 ('List') and resource ('alerts'), and clarifies the scope as either personal alerts or a group's alerts. It does not explicitly name the sibling tools it differs from, but the listing semantics make it distinguishable from alerts_raise and alerts_update.

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 gives a useful precondition for group-scoped listing ('Requires current group membership') and implies that omitting the group yields personal alerts via the schema. However, it does not mention when not to use this tool or point to sibling alternatives for related operations.

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