vsphere_list_alarms

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

Annotations already establish the tool as read-only, idempotent, and non-destructive. The description adds useful behavioral context by clarifying that it returns only currently triggered alarms (not historical) and covers the entire inventory, with optional filtering. This goes beyond the structured annotations without contradicting them.

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 compact and front-loaded with the core purpose in the first sentence, followed by a use-case note and a concise Args list. Every sentence carries value, and the structure makes it easy to scan.

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?

The tool is a straightforward listing operation with an output schema available. The description covers purpose, usage context, and semantics for all four optional parameters, so the agent has everything needed to select and invoke it correctly. No important context is missing.

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?

Even though the schema descriptions provide 0% coverage, the description fully documents each parameter: status with red/yellow severity values, include_acknowledged, limit, and offset. This adds meaningful detail—especially the severity values—that the schema alone does not provide.

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 begins with 'List every currently triggered alarm across the inventory,' which clearly specifies the verb (list), resource (alarms), and scope (currently triggered across the inventory). This distinguishes it from sibling tools like vsphere_list_events and vsphere_list_tasks.

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 phrase 'This is the fastest way to answer "what is unhealthy right now"' provides strong contextual guidance for when to use this tool. However, it doesn't explicitly name alternative tools for other scenarios, like vsphere_list_events for historical event analysis, so it stops short of full exclusionary guidance.

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