export_alarm_csv

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

Annotations already declare readOnlyHint=true and destructiveHint=false. The description adds value by specifying the return format (CSV text with header), the default limit (2000), and a usage tip. No contradictions; it enriches behavioral context.

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 well-structured with a bold lead, bulleted parameters, and a tip. It is front-loaded with the purpose and uses emoji for emphasis. Slightly verbose but effectively organized.

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 no output schema, the description adequately explains the return value (CSV text). It covers parameters, output format, and usage tips. Missing error handling or performance notes, but sufficient for a read-only export tool.

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%, but the description provides extra clarity with a format example for startTime, enumerates alarmType values, and confirms the limit default. This goes beyond the schema's basic descriptions.

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 exports alarm records as CSV text for pasting into Excel, specifying verb (export), resource (alarms), and format (CSV). It distinguishes from sibling 'list_alarms' by emphasizing batch export and Excel compatibility.

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 provides context for using the tool (copy-paste to Excel) but lacks explicit guidance on when to choose this over alternatives like 'list_alarms' or when not to use it. No exclusions or prerequisites are mentioned.

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