get_alarms

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

No annotations are provided, so the description carries full burden. It states the tool is deprecated and queries alarms with filters, but lacks details on pagination, default behavior, or result handling. The deprecation note adds transparency, but behavioral specifics are minimal.

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 two sentences: a deprecation warning and a purpose statement. It is front-loaded with the most critical information (deprecation) and contains no fluff. Efficient and direct.

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?

Given the tool is deprecated, the description adequately covers the deprecation context and directs to the replacement. For a deprecated tool, it is complete. If active, it would lack details on return values and pagination, but the deprecation lowers the requirement.

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 coverage is 100%, so the schema already documents all parameters. The description only adds that filtering is supported by level, status, time range, which is already evident from the schema. No additional semantic value beyond the schema.

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 tool is deprecated and to use get_warnings instead, while also indicating it queries alarm lists with filtering capabilities. This provides a specific verb (query), resource (alarm list), and distinguishes from the sibling get_warnings.

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 explicitly advises to use get_warnings instead, giving clear when-not-to-use guidance. It also mentions filtering support, indicating suitable use cases. This is highly explicit for usage context.

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