get_metric

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

The description implies a safe read-only operation ('Get details') but does not explicitly state behavioral traits. With no annotations provided, the description carries the full burden; it lacks mentions of permissions, error behavior, or side effects. However, for a simple retrieval, the implication is acceptable.

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, concise sentence. It is front-loaded with the purpose. While it could benefit from additional parameter details, it remains efficient for a simple tool.

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 low complexity (2 params, no output schema), the description provides a basic understanding but omits explanation of the fields parameter and return value format, which are important for an agent to use the tool correctly.

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 description only mentions the metric_id parameter implicitly ('by ID'), but does not explain the 'fields' parameter. Since the input schema has 0% description coverage, the description fails to add meaning for the fields parameter, leaving the agent without guidance on its purpose.

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 tool retrieves details of a metric by ID, using specific verb and resource. It distinguishes from siblings like 'get_metric_by_name' by specifying the retrieval method.

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 this tool versus alternatives. The description does not mention that this tool requires a metric ID, unlike 'get_metric_by_name' which uses a name. The agent receives no when-to-use or when-not-to-use context.

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