zdx_get_deeptrace_cloudpath_metrics

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

Annotations already declare readOnlyHint=true and openWorldHint=false, and the description repeats the read-only nature. It adds useful context by describing the response shape as 'curated, nested time-series JSON', which is not present in annotations or schema. 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 with no filler content. Every phrase adds value, including the return-format hint and read-only note.

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 the lack of an output schema, the description's note about 'curated, nested time-series JSON' provides essential expectation-setting. Combined with the schema's detailed query parameter explanation, this is mostly complete for a straightforward read-only getter, though it omits details like pagination or limits.

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?

With only 33% schema description coverage, the description needed to clarify trace_id and device_id, but it only hints at trace context. The detailed query parameter documentation exists in the schema, not in the description, so the description fails to compensate for the low coverage.

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 uses a specific verb ('Get') and identifies the exact resource ('cloud-path metrics') plus the context ('during a ZDX deep trace'), distinguishing it from sibling tools like zdx_get_deeptrace_cloudpath, zdx_get_deeptrace_health_metrics, and zdx_get_deeptrace_webprobe_metrics.

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 clearly states that this tool returns cloud-path metrics from a deep trace, giving context for when to use it. It does not explicitly name alternatives or exclusions, so it falls short of full usage guidance but is not merely implied.

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