zdx_get_deeptrace_health_metrics

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

The description labels the tool as 'read-only', which matches the readOnlyHint annotation. However, it does not add additional behavioral context beyond what the annotation already provides, such as potential side effects or error conditions.

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 at 10 words, with no redundant information. It is front-loaded with the key action and resource.

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 tool is a simple read operation with an output schema, so the description is sufficient. However, it could benefit from a brief note on required parameters or typical use cases, but the required parameters are already marked in the schema.

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?

All three parameters are documented in the input schema with descriptions. The description adds no additional meaning to the parameters beyond stating the overall purpose. With 100% schema coverage, 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 it retrieves health metrics from a ZDX deep trace session, which is specific and distinguishes it from sibling tools like zdx_get_deeptrace_events or zdx_get_deeptrace_cloudpath.

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 on when to use this tool versus other deep trace tools (e.g., for events, cloudpath metrics, or webprobe metrics). The description only states what it does, not when it is appropriate.

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