zdx_get_application_metric

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

The description includes 'read-only', which matches the readOnlyHint=true annotation. No additional behavioral traits (e.g., error conditions, data freshness) are disclosed. The annotation already carries the safety profile, so the description adds minimal extra 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, front-loaded sentence that efficiently communicates the core purpose. No waste or redundancy.

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 is minimal; it does not mention the available metrics (pft, dns, availability) or the optional filters (location, department, geo, time), which are defined in the schema. Given the tool has 7 parameters and an output schema, the description could provide more high-level context to help the agent understand the tool's scope.

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 input schema covers all 7 parameters with descriptions, achieving 100% schema description coverage. The tool description does not add any parameter meaning beyond what the schema provides, so a 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 verb 'Get' and the resource 'ZDX metrics for a specified application'. It also labels the tool as 'read-only', which aligns with the annotation. However, it does not differentiate this tool from siblings like 'zdx_get_application_score_trend' or 'zdx_get_application', which have similar purposes.

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 provides no guidance on when to use this tool versus alternatives. With many sibling tools for different metrics and applications, the agent lacks context for selection.

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