zdx_get_deeptrace_events

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

Annotations already declare readOnlyHint=true and openWorldHint=false, and the description reaffirms 'Read-only.' It adds a small behavioral detail about the return format ('curated, nested JSON with ISO timestamps'), but does not disclose other traits like pagination, size limits, or error behavior. Since annotations cover safety, a baseline of 3 is appropriate.

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 a single, well-structured sentence that conveys core purpose and output format without fluff. It is front-loaded with the action and resource, and every clause adds value.

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 tool with two required parameters, no output schema, and low parameter coverage, the description is insufficient. It lacks usage guidance, parameter explanations, and behavioral details beyond the bare minimum. The presence of annotations and a few keywords does not fill the gaps completely.

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 only 33% (only 'query' has a description). The tool description itself does not explain any parameter meanings or relationships. It fails to compensate for the low coverage, leaving trace_id and device_id completely unaddressed.

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 action: 'Get the events captured during a ZDX deep trace' with a specific resource and purpose. It also adds useful context about the output format ('curated, nested JSON with ISO timestamps'), which distinguishes it from sibling tools like zdx_get_deeptrace_cloudpath and zdx_get_deeptrace_health_metrics that return different data.

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 no guidance on when to use this tool versus alternatives. It does not mention prerequisites, scenarios, or exclusions. While the naming suggests it is for deep trace events, there is no explicit direction about when to choose this over sibling tools.

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