zdx_get_deeptrace_cloudpath

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

Annotations already declare readOnlyHint=true, so the 'Read-only' repetition adds no new safety information. The description does add a small behavioral detail—'curated, nested JSON'—hinting at the response shape and processing level, but does not disclose permissions, trace prerequisites, or return structure. No contradiction with annotations.

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 front-loaded sentence that defines the tool's purpose in 17 words. The trailing 'Read-only' is redundant given the readOnlyHint annotation, but it does not materially hurt clarity or structure.

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 getter with no output schema, the description gives the essential resource (cloud-path) and a hint of response format ('curated, nested JSON'), but leaves return fields, how to obtain trace_id/device_id, and prerequisites unspecified. The optional query documentation helps, but the missing output schema and dependency info leave moderate gaps.

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 query parameter has rich schema-level description with JMESPath examples and a critical snake_case warning, adding significant meaning beyond the schema. However, device_id and trace_id are only named in the schema with no semantic detail; they are self-explanatory by name and context, but the description does not explicitly connect them to the deep-trace context.

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?

Description uses specific verb 'Get' and resource 'cloud-path' defined as 'hop-by-hop network path captured during a ZDX deep trace,' clearly distinguishing it from sibling metric/event tools by naming the exact data returned. The 'curated, nested JSON' qualifier further clarifies output form.

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?

No explicit guidance on when to use this tool versus alternatives such as zdx_get_deeptrace_cloudpath_metrics or zdx_get_device_deep_trace. The phrase 'captured during a ZDX deep trace' implies a prerequisite but does not state exclusions, prerequisites for trace_id, or why 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.