search_alarms

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

No annotations provided, but description covers search behavior, filter capabilities, pagination via cursor, default and max limits, sorting, and grouping. Missing non-critical details like rate limits or return structure.

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?

Efficiently structured with clear sections, though listing 16 alarm types adds length. Each sentence contributes necessary information; front-loads purpose and syntax.

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?

Input side is well-covered, but output schema is absent and description does not explain return format or pagination details beyond cursor mention, leaving some completeness gaps.

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%, and description adds substantial value beyond schema by explaining query syntax, examples, field values, and enumeration of alarm types, exceeding baseline.

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?

Description clearly states 'Search alarms using full-text or field filters' and lists all alarm types with numeric IDs, making the tool's purpose specific and distinguishable from siblings like get_active_alarms or get_specific_alarm.

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?

Provides detailed query syntax, examples, and field descriptions, guiding effective usage. However, lacks explicit when-to-use vs alternatives or when-not-to-use scenarios.

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