zdx_get_alert

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

Annotations already declare readOnlyHint=true. The description adds beyond annotations by stating the output is a 'curated, agent-facing detail view' and that it 'adds the impacted department/location/geolocation scope.' No contradictions; provides additional 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 two sentences, front-loading the purpose and then adding behavioral details. Every sentence earns its place without redundancy or fluff.

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 tool's simplicity (one required string parameter, read-only, no output schema), the description adequately covers the return value ('curated detail view with added scope'). No missing essential information for an agent to use the tool correctly.

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?

There is only one parameter 'alert_id' with 0% schema description coverage. The description does not explain that 'alert_id' is the required identifier or what format it expects. While the purpose implies its necessity, the description adds no semantic value beyond the schema's existence.

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 ('Get'), the resource ('one ZDX alert'), and the nature of the output ('curated, agent-facing detail view'). It distinguishes itself from sibling tools like 'zdx_list_alerts' by focusing on a single alert with additional scope enrichment.

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 explicitly marks the tool as 'Read-only,' but does not provide explicit when-to-use or when-not-to-use guidance compared to siblings. However, the context implies it is for retrieving a single alert with enriched fields, which contrasts with list tools. Lacks explicit alternatives.

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