zdx_get_device_deep_trace

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

Annotations already declare readOnlyHint=true and openWorldHint=false, but the description adds valuable behavioral context: the SDK returns a single-element list, unwraps the trace record, ISO-normalizes timestamps, and shapes to identity fields. This goes beyond annotations without contradicting them.

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?

Three sentences, no wasted words. The first sentence states the core purpose, followed by concise behavioral notes. Each sentence earns its place.

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 no output schema, the description explains return format (single-element list, unwrapped, normalized) but does not clarify what a deep-trace session is or detail response fields. Prerequisites (e.g., valid device_id and trace_id from a list) are missing. Adequate but incomplete.

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 0% (no descriptions in schema). The description does not explain the parameters (trace_id, device_id) beyond the tool's purpose. While the names are somewhat self-explanatory, the description adds no additional meaning about their format, source, or constraints.

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 'Get one ZDX deep-trace session,' specifying the verb (Get) and resource (deep-trace session). This distinguishes it from sibling tools like zdx_list_device_deep_traces (list) and other getters for different resources.

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 usage for retrieving a single deep trace session but does not explicitly state when to use it versus alternatives, such as zdx_list_device_deep_traces for listing or other getters for different trace types. No when-not-to-use or prerequisites are mentioned.

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