zdx_get_application_metric

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

Annotations indicate readOnlyHint=true, and the description redundantly states 'Read-only' but adds behavioral details: returns one series per metric with datapoints over a time window, and supports narrowing by metric_name. The description adds value beyond annotations.

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?

Three sentences, front-loaded with purpose, no unnecessary words. Efficient and clear.

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?

No output schema, but description explains return format (series per metric, datapoints). Missing details on pagination, error handling, and unmentioned parameters. Adequate but not comprehensive for 7-parameter 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?

Only 14% schema coverage. The description explains `since` (hours window, default 2h) and `metric_name` (enum values), but other parameters like geo_id, location_id, department_id are not described. Partial compensation for low schema coverage.

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 gets ZDX performance metrics for one application as time-series data, listing specific metrics (Page Fetch Time, DNS Time, availability). It distinguishes from sibling tools like zdx_list_applications by referencing app_id from that tool.

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?

Provides clear usage guidance: use app_id from zdx_list_applications, optionally filter by metric_name, and note the default since window of 2 hours. Does not explicitly mention when not to use or alternatives, but the context is sufficient.

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