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

readOnlyHint=true already tells the agent this is a safe read, so the bar is lower. The description adds that the data is time-series covering throughput/latency/replicas, which is useful, but says nothing about return shape, granularity, or whether an empty range returns an error — reasonable but not rich.

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?

Two front-loaded sentences with zero padding: the metric content and scope come first, the endpoint mapping second. Nothing is redundant or misplaced.

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?

There is no output schema, so the description partially compensates by naming the three metric families returned. It still leaves time-series granularity and response structure unstated, but for a simple read-only stats tool with fully documented params this is nearly sufficient.

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?

Schema description coverage is 100%: deploy_id, from and to are all documented in the schema with format hints (unix timestamp or relative expression, units s/m/h/d/w). The description adds no parameter detail beyond the REST path naming deploy_id, so baseline 3 applies.

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?

States a specific verb ('Get') and resource ('time-series stats') and enumerates the metrics returned (throughput / latency / replicas), scoped to a dedicated deployment. It does not explicitly contrast itself with the sibling deepinfra_get_live_metrics, but the 'time-series' qualifier implicitly separates it from a live-snapshot 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?

The phrase 'for a dedicated deployment' implies the applicable context, and the REST endpoint reference confirms the underlying operation. However, there is no explicit when-to-use statement, no exclusions, and no naming of the alternative (e.g. deepinfra_get_live_metrics) that an agent should pick for real-time data.

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