List Alert Routing Rules

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is covered. The description adds only the endpoint-selection caveat and says nothing about pagination, result ordering, or volume, which matters given page_size/page_number/sort params.

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 the action front-loaded and the caveat second. Efficient, though the bolded support-escalation note consumes space without adding invocation-relevant detail.

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?

An output schema and annotations cover return shape and safety, but an 18-parameter listing tool with zero schema descriptions needs the description to explain filter semantics and pagination, and it does none of that. An agent could call it, but only by guessing at the parameter vocabulary.

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?

There are 18 parameters with 0% schema description coverage, and the description mentions none of them. It provides no guidance on filter_name* vs filter_slug* variants, include, sort syntax, or date filter formats, leaving the agent to infer everything from terse parameter names.

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 names a specific verb and resource ("List alert routing rules") and distinguishes the tool from the sibling Alert Routes endpoint. It does not, however, differentiate from other close siblings like get_alert_routing_rule or create_alert_routing_rule beyond the implied list semantics.

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 explicitly routes advanced alert routing users to a different endpoint and tells uncertain users to contact support. That is real when-not guidance, though it does not state when the tool is the correct choice for non-advanced users or what "advanced" means operationally.

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