list_metrics

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

Discloses that this endpoint may be unavailable on Gen3/Grail tenants - a key behavioral trait. No annotations provided, so description carries full burden; it adds helpful context beyond pure functionality.

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, front-loaded with purpose and filter example. No extraneous words.

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?

For a list/search tool with no output schema, the description adequately covers purpose, usage, filtering, and platform-specific availability. Complete enough for agent decision-making.

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%, so baseline is 3. Description gives an example for metricSelector ('builtin:host.*') which adds value, but pageSize is not elaborated beyond schema.

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?

Clear verb+resource: 'List/search metric descriptors (classic Metrics v2)'. Distinguishes from siblings like query_metric and execute_dql which serve different purposes.

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?

Explicitly provides usage context: filtering with metricSelector, and explicitly warns when not to use on Gen3/Grail tenants and gives alternatives (query_metric, execute_dql).

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