get_active_alerts

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

No annotations are provided, so the description carries the full burden. 'List' implies a read-only operation, and no side effects or limitations are hidden. However, it does not disclose behavioral details such as output sorting, pagination, or definition of 'active', though these are minor for a simple list.

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?

A single concise sentence that is front-loaded with the action, zero filler, and no repetition of schema properties.

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 simple two-parameter read-only tool and the presence of an output schema, the description sufficiently covers the core functionality and optional filtering. It lacks only minor contextual guidance such as sourcing plant_id from list_plants, which is not critical.

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 0%, so the description must compensate. It adds meaning by linking 'plant' to plant_id and 'optionally filtered by minimum severity' to min_severity, explaining the filter concept. It does not elaborate on enum values or defaults, but the schema provides those.

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 verb 'List', the resource 'active alerts', and the scope 'at a plant', distinguishing it from sibling tools that handle plants, silos, thermometry, motors, and motor actions.

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 clear context for when to use the tool: when active alerts for a plant are needed. While it does not explicitly name alternatives or exclusions, the sibling tools are clearly different resources, so usage is unambiguous.

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