metrics_trends

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

No annotations are provided, so the description carries the full burden. It discloses the aggregation shape (bucketed intervals over time) and the three metric families, which is useful. However, it says nothing about the default window, maximum range behavior, cost, or the shape of the returned series—gaps that matter for a query tool with zero annotation coverage.

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 sentences, zero filler, with the resource and metric scope front-loaded and the intent following immediately. Every sentence earns its place.

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 annotations and no output schema, the description should ideally say something about the return shape (per-bucket series per metric) and default behavior. It covers what data is produced but not how it comes back, leaving an analysis-oriented agent to guess at the response structure.

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% and both parameters are documented in the schema (minutes default 60, project_id with a hint to call list_projects). The description's only added semantic is "bucketed intervals," which loosely relates to the minutes window but does not explain bucket granularity or how the window maps to buckets.

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 concrete verb-like action (view trends) and names the three metrics returned (request volume, error rate, latency) over bucketed time intervals. It is distinguishable from siblings like metrics_distributions or metrics_summary by its time-series focus, but it never names those siblings to sharpen the distinction.

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?

"Call this to understand how performance has changed and spot degradation or recovery patterns" gives a usage intent, but there is no explicit when-not guidance and no comparison to metrics_overview, metrics_summary, or metrics_levels, which an agent must choose between. Usage is implied rather than routed.

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