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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safe-read profile is fully covered externally. The description adds domain context about what destinations mean per scope but says nothing extra about auth requirements, rate limits, or pagination behavior, so a mid score is right.

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?

A single front-loaded sentence delivers scope semantics, and a second short sentence routes to the alternative, followed by a docs link. Nothing is redundant and no clause could be dropped without losing meaning.

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?

Output schema exists, so return values need no explanation, and annotations fully cover the safety profile. With purpose, scope semantics, and the sibling alternative all stated, an agent has everything needed to select and invoke this tool correctly.

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 baseline is 3, and the description exceeds that by explaining what each scope value actually returns rather than merely restating the enum. It still does not restate the conditional requirement of tag_name/monitor_id, which the schema already carries.

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?

States a specific verb+resource ("List where Oh Dear sends alerts") and then defines the three scope values so the agent knows exactly what is being listed for each case. It also explicitly names the sibling it is not (list_tag_groups), making it distinguishable without opening any schema.

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?

Gives explicit per-scope usage semantics ("team" = team-wide alerts, "tag" = alerts for monitors carrying a tag, "monitor" = a single monitor's alerts) plus a named alternative for tag-group routing. The agent has both the when and the when-not.

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