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

Annotations already declare readOnlyHint and openWorldHint, so the bar is lower, yet the description still adds the required scope (vms.read) and the bucket granularity for each range. It does not discuss cost, rate limits, or partial-data behavior, but the auth scope disclosure is meaningful extra context.

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?

One dense sentence that front-loads the returned metrics and then the time-range semantics, followed by a short scope note. No padding, though the telegraphic style makes the range mapping slightly harder to parse on first read.

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?

With no output schema, the description usefully enumerates the returned series and mentions totals. The main remaining gap is the behavior when the optional range parameter is omitted (default window), which an agent must know to get predictable results.

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 coverage is 50%: the lb parameter is documented in-schema but range is a bare enum. The description compensates by mapping each range to its bucket size (1-minute, 15-minute, 1-hour), which is exactly the information an agent needs to choose a range and interpret the series.

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 names the resource and enumerates the exact metrics returned (requests by response class, connections, bytes in/out, peak sessions, totals), which is far more specific than the tool name alone. It is distinguishable from get_vm_metrics and get_database_metrics by the metric set, though it never states 'load balancer' explicitly because that is carried by the name/title.

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?

Usage is implied: this is the companion to get_load_balancer for time-series data. There is no explicit statement of when to call this versus get_load_balancer or the other metrics tools, and no note about what to do when range is omitted.

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