list-logs-metrics

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

The description is basic and does not disclose any behavioral traits beyond the surface-level action. With no annotations provided, it carries the full burden but fails to mention read-only nature, authentication needs, or potential pagination behavior.

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?

The description is a single sentence of 8 words, front-loaded with the action and resource. No unnecessary 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 parameterless list tool, the description is fairly complete. It states what is returned (metrics with definitions). However, no output schema exists, so the description could be more detailed about the structure of definitions. Still, given the simplicity, it is adequate.

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?

The input schema has no parameters, so schema coverage is 100%. The description adds no parameter info since there are none. Baseline 4 is appropriate.

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 states the verb 'List' and the resource 'configured log-based metrics' with 'their definitions', clearly specifying the action and object. It distinguishes from siblings like get-logs-metric (single item) and create-logs-metric (create).

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 description implies usage for listing all log-based metrics, but does not explicitly state when to use this tool versus alternatives like get-logs-metric for a specific metric. No when-not-to-use or alternative recommendations are given.

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