metrics_metric_get

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

With no annotations, the description must disclose behavioral traits. It states the return value ('full metric dict') and error behavior ('or an error if not found'). However, it does not mention side effects (likely none), authorization requirements, or performance characteristics, leaving gaps for an agent.

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 two sentences, front-loaded with the primary action and a brief return note. Every sentence adds distinct value without redundancy, making it highly efficient.

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?

Given the tool's simplicity (one required parameter, output schema exists), the description covers the core behavior but lacks guidance on when to use it and does not elaborate on parameter semantics. The output schema reduces the need to describe return details, but the overall completeness is adequate but not thorough.

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 0%, so the description must compensate. It implicitly refers to the 'name' parameter through 'specific metric', but provides no additional constraints, format, or examples. This adds minimal value beyond the schema's 'Name' title and type string.

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 clearly states the action: 'Get the current state of a specific metric.' It uses a specific verb ('Get') and resource ('metric state'), and distinguishes from sibling tools like metrics_metric_list (list all) or metrics_metric_export (export) by focusing on a single metric by name.

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 explicit guidance on when to use this tool versus alternatives. For example, it doesn't mention that metrics_metric_list should be used to retrieve all metrics, or that metrics_metric_get is for individual queries. This omission forces the agent to infer usage from names alone.

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