list_alert_definitions

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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true, openWorldHint=true. The description adds behavioral context by noting that criticality is derived from states[] and that AlertDefinition has no top-level criticality/enabled fields, which aids agent understanding.

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 relatively concise, starting with a clear purpose annotation '[READ]', then a model clarification, followed by parameter details. Some redundancy exists (e.g., repeating limit default), but overall well-structured and front-loaded.

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?

With an output schema present, return values are covered. The description provides necessary parameter defaults and model nuance. For a list tool with good annotations, this is complete enough, though it could briefly mention pagination or ordering.

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 0%, so the description fully explains parameters: name_filter (substring, case-insensitive), limit (range 1-500, default 100), target (Aria Operations target name from config). This adds significant meaning beyond the schema's bare properties.

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 'List alert definitions (templates that generate alerts when triggered)', specifying the verb and resource. It distinguishes this tool from siblings like list_alerts by emphasizing 'definitions' as templates.

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 alert definitions but does not explicitly state when to use this tool versus alternatives like list_symptom_definitions or get_alert. No when-not-to-use or exclusions are provided.

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