zdx_get_deeptrace_webprobe_metrics

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

The description includes '(read-only)', which duplicates the readOnlyHint annotation. Beyond that, it does not disclose any behavioral traits such as what data is returned, any limitations, or how the metrics relate to the deep trace session. With annotations already covering read-only, the description adds minimal value.

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, brief sentence that directly states the tool's purpose. It is front-loaded with the action and resource, with no wasted words.

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?

While the description is minimal, the output schema exists (as indicated) and parameters are well-documented in the schema. However, given the large number of sibling tools with similar purposes, more context about what web probe metrics are and how they differ from other deep trace metrics would improve completeness.

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 100%, with each parameter having a description in the schema. The tool description adds no additional semantic meaning beyond what the schema already provides, so the baseline score of 3 is appropriate.

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 the action: 'Get web probe metrics from a ZDX deep trace session'. It specifies the resource (web probe metrics) and the context (deep trace session), and the '(read-only)' qualifier adds clarity. This distinguishes it from sibling tools like zdx_get_deeptrace_cloudpath_metrics or zdx_get_deeptrace_health_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 offers no guidance on when to use this tool versus alternatives. There is no mention of prerequisites, comparison with other metric tools, or scenarios where web probe metrics are appropriate.

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