List alerts

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false, so the safety profile is covered. The description adds useful behavior beyond annotations: status is filtered by Atera, while severity/customer/agent filters scan up to maxPages pages. It does not cover rate limits or return format, but the added filtering behavior is meaningful.

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?

Two sentences, front-loaded with the core action followed by the key filtering behavior. There is no wasted wording, and the pagination/filter constraint is stated directly.

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?

For a 9-parameter tool with no output schema, the description is minimal but adequate in places. It explains the scan behavior for some filters and relies on schema descriptions for pagination fields. However, it omits guidance on when to use the tool and does not fully clarify the relationships among page, limit, itemsInPage, and maxPages.

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 description coverage is 67%, so the schema documents most parameters. The description adds value for status, severity, customer, and agent filters by explaining that they scan up to maxPages pages, but it omits full, page, limit, and itemsInPage. It partially compensates for the coverage gap.

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 states a specific verb and resource: 'List alerts.' This distinguishes it from the singular sibling get_alert by name, though it does not explicitly call out the distinction. A clear purpose, but sibling differentiation is left to the name.

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 says nothing about when to use list_alerts versus get_alert or other listing tools. It provides filter behavior, but no usage context, prerequisites, or alternatives are given.

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