list-active-metrics

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

Annotations provide readOnlyHint and openWorldHint. The description adds that it lists metrics from a given time with optional filters but does not disclose additional behavioral traits like pagination, definition of 'active', or rate limits. No contradiction with 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?

Single sentence, 15 words, front-loaded with action and resource. Every part is relevant and concise with no 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?

Adequate for a simple read tool with three parameters and no nested objects, but lacks details on what 'active' means, return format, or pagination. Without an output schema, the description could provide more context about 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 coverage is 100%, with descriptions for 'from', 'host', and 'tagFilter' already present. The description merely restates these parameters ('from a given time, optionally filtered by host or tag') without adding new meaning or constraints.

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?

Description clearly states 'List active metrics' with a specific verb and resource. It specifies the temporal scope ('from a given time') and optional filters. While distinct from siblings like 'list-metric-tags' and 'get-metrics', it could more explicitly differentiate the concept of 'active' metrics from listing all metrics.

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?

No guidance on when to use or not use this tool versus alternatives. Sibling tools include 'list-metric-tags', 'list-hosts', 'query-metrics', etc., but the description does not indicate when this tool is preferred or any prerequisites.

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