zdx_get_deeptrace_webprobe_metrics

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

In addition to the readOnlyHint annotation, the description usefully discloses that the output is a curated, nested time-series JSON structure. This adds meaningful behavioral context since there is no output schema, though it does not cover pagination or detailed response shape.

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. It covers the action, the resource type, the capture context, and the safety profile without repeating unnecessary information.

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?

The description provides a meaningful output hint for a tool with no output schema, and the complex query caveat is already handled in the input schema. It could be more complete with a cross-reference to sibling deep-trace metric tools, but the core invocation path is sufficiently clear.

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 low and the description does not add much meaning for device_id and trace_id beyond implying they come from a deep trace context. The optional query parameter, however, receives very detailed guidance in the schema itself, which partly compensates for the tool description's brevity.

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 names a precise resource — web-probe metrics — and scopes it to ZDX deep traces, which differentiates it from sibling tools like zdx_get_deeptrace_health_metrics or zdx_get_web_probes. The verb 'Get' and 'Read-only' make the access intent 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 clearly indicates when the tool applies: when web-probe metrics from a ZDX deep trace are needed. It does not name alternatives or explicitly say when not to use it, but the contextual scope is clear enough for selection.

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