zdx_list_historical_alerts

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

Description explicitly states 'Read-only', aligning with annotations. Adds behavioral context for the `since` parameter (hours, defaults, max). Does not disclose pagination or rate limits, but for a read-only list tool, this is adequate.

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?

Extremely concise: three lines covering purpose, read-only status, sibling distinction, and a key parameter. No filler. Front-loaded with the action.

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?

Lacks descriptions for most parameters and does not mention pagination or return format. While the comparison to `zdx_list_alerts` helps, the tool could be more self-contained. The absence of output schema means the description should compensate more.

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 only 14% (1 of 7 parameters described). The description adds meaning for `since` (hours, default, max) but does not describe other key parameters like limit, offset, geo_id, location_id, department_id. Given low coverage, more parameter information would be expected.

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?

Clearly states 'List historical (ended) ZDX alerts.' and distinguishes from sibling `zdx_list_alerts` by specifying it is for alerts with an Ended On date. The verb and resource are explicitly defined.

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 clear usage context: use for ended alerts, not for active ones (inferred from sibling comparison). Also specifies the `since` parameter in hours with default and maximum, guiding temporal scope.

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