list_alert_grouping_settings

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

Annotations already indicate readOnlyHint=true, destructiveHint=false, idempotentHint=true. The description adds no behavioral context beyond 'List all', but fails to mention pagination behavior (schema includes limit/after/before), which could mislead an agent into expecting a single unfiltered list.

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 short and structured with Args/Returns. It could be slightly more concise by omitting the redundant block since schema and output schema exist, but overall it is efficient.

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?

Despite having an output schema and annotations, the description lacks important context about pagination behavior (e.g., results are paginated, use cursors). The statement 'List all' is misleading given the pagination fields. The description is insufficiently complete for an agent to understand the tool's full behavior.

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 description only says 'query_model: Optional filtering parameters', which adds no value beyond the schema. However, the schema itself provides full descriptions for all nested fields, so the tool description need not repeat them. Baseline 3 is appropriate.

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 clearly states the action ('List') and the resource ('all alert grouping settings'), and it distinguishes from the sibling tool 'get_alert_grouping_setting' which retrieves a single setting. The purpose is unambiguous.

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 implies usage for listing with optional filtering but does not explicitly state when to use this tool versus alternatives like 'get_alert_grouping_setting' or other list tools. No when-not-to-use guidance is provided.

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