zdx_get_alert

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

Annotations already provide readOnlyHint=true, and 'Read-only' merely repeats this. However, the description adds useful behavioral context by explaining that the detail view enriches the summary fields with impacted department/location/geolocation scope, going beyond the raw annotation data.

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 short sentences, with the main purpose front-loaded and the second sentence adding read-only status and unique output scope. No wasted words.

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 simple get-by-ID tool with readOnlyHint and openWorldHint annotations, the description provides enough to select and invoke it correctly. It could explicitly mention obtaining alert_id from zdx_list_alerts, but given no output schema and a single obvious parameter, the gap is minor.

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?

The only parameter, alert_id, is self-explanatory by name, but schema description coverage is 0% and the description provides no guidance on the ID's source, format, or relationship to zdx_list_alerts. Since coverage is low and the description does not compensate, parameter semantics are weak.

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 a specific verb and resource: 'Get one ZDX alert' as a 'curated, agent-facing detail view.' This distinguishes it from list-style siblings like zdx_list_alerts and gives a precise sense of what the tool does.

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 implies when to use the tool: when a single alert's detailed, agent-facing view is needed. It does not explicitly name alternatives or exclusions, but the context is clear enough from the wording and the sibling list.

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