zdx_get_deeptrace_events

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

Annotations already declare readOnlyHint=true, so the description adds value by specifying the output format (curated, nested JSON with ISO timestamps). However, it lacks details on pagination, limits, or required permissions beyond the annotation.

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 very concise, consisting of a single sentence and a fragment. It front-loads the purpose. However, it could be more structured to include parameter hints or example usage.

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 three parameters, no output schema, and some schema description gaps, the description is incomplete. It does not explain the return structure beyond 'curated, nested JSON', lacks pagination info, and does not provide examples for the query parameter.

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 description). The description does not explain the parameters device_id or trace_id, nor does it clarify how to obtain them or their meaning. This is insufficient for correct parameter usage.

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 tool retrieves events from a ZDX deep trace and mentions the data format (curated, nested JSON with ISO timestamps). However, it does not differentiate from sibling tools like zdx_get_device_deep_trace or zdx_list_deep_traces, which may also return events.

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 only notes 'Read-only', which hints at safe usage but gives no explicit guidance on when to use this tool versus alternatives, no prerequisites, and no conditions for use.

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