zdx_get_deeptrace_health_metrics

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

Annotations already declare readOnlyHint=true, so the description's 'Read-only' adds no new behavioral information. It does mention 'curated, nested time-series JSON', but lacks details on output structure, error behavior, or prerequisites.

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 very short (one sentence plus 'Read-only') and to the point, which is good for conciseness. However, it may be oversimplified given the tool's complexity and lack of output schema.

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 basic idea of the tool's purpose and output type, but without output schema or more details on return format, pagination, or limits, it is minimally adequate for a simple read-only tool.

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 has 3 parameters with only 33% coverage (query described). The description does not explain device_id or trace_id beyond their names, missing an opportunity to clarify their roles or format. Given low coverage, description should compensate but does not.

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 tool retrieves device health metrics from a ZDX deep trace and specifies the output as curated nested time-series JSON. It differentiates from siblings by focusing on health metrics, but does not explicitly name alternative tools or contrast them.

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 like zdx_get_deeptrace_events or zdx_get_deeptrace_cloudpath_metrics. The only hint is 'Read-only', which implies safety but does not help with selection.

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