zdx_get_deeptrace_webprobe_metrics

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

The description adds that the data is curated and in nested time-series JSON format, which provides useful behavioral insight. Since annotations already declare readOnlyHint=true, the description does not need to repeat that. However, it does not disclose other behavioral traits like pagination, rate limits, or authentication needs. The added value is moderate.

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 extremely concise, consisting of a single sentence of 14 words. It front-loads the core purpose. However, it may be too sparse for a tool with multiple parameters and no output schema, but for the purpose of conciseness, it is efficient.

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 that there is no output schema and only 33% schema description coverage, the description should provide more context about the return value structure and parameter usage. It mentions 'curated, nested time-series JSON' but does not specify which metrics are included or how to interpret the nested structure. The description is incomplete for effective tool usage.

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 schema description coverage is only 33% (only the 'query' parameter has a description). The tool description does not add any meaning to the 'trace_id' and 'device_id' parameters beyond what is in the schema. The description of 'query' is already detailed in the schema, so no additional value is provided by the tool description.

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 verb 'Get' and the resource 'web-probe metrics captured during a ZDX deep trace'. It also mentions the curated, nested time-series JSON format, making the purpose specific. However, it does not explicitly differentiate this tool from similar siblings like zdx_get_deeptrace_cloudpath_metrics or zdx_get_deeptrace_health_metrics, though the name itself provides some distinction.

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 guidance is provided on when to use this tool versus alternatives. The description only states it is read-only, which is already declared in annotations. No exclusions or context for preferred usage are given.

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