zdx_get_device_deep_trace

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

Annotations already declare readOnlyHint=true, and the description adds behavioral context by explaining that the SDK returns a list but the tool unwraps it, normalizes timestamps, and shapes identity fields. This goes beyond the annotation and prepares the agent for response transformation.

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 brief and well-structured: a clear purpose sentence, a one-word read-only note, and a compact explanation of SDK behavior. Every sentence adds value, with no repetitive or irrelevant content.

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 read-only get operation with two self-explanatory parameters and no output schema, the description covers the core behavior including the unexpected list unwrapping and timestamp normalization. It lacks explicit parameter explanations and usage alternatives, but remains adequate for such a simple tool with strong annotations.

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 input schema has no parameter descriptions (0% coverage), and the description does not explain trace_id or device_id. The parameter names are self-explanatory, but no additional semantic meaning is provided, so the description fails to compensate for the missing schema descriptions.

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 opens with 'Get one ZDX deep-trace session,' specifying a clear verb and resource. It explicitly distinguishes from the sibling 'zdx_list_device_deep_traces' by emphasizing a single session, making the purpose unambiguous.

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, contrasting with list operations, but it does not explicitly state when to use this tool over alternatives or provide any exclusions. No sibling tool is named, so guidance is only implied.

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