list_metrics

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

No annotations are provided, so the description carries the transparency burden. It discloses the output shape (id, label, definition, dimensions) and the semantic rule about nonexistent metrics. However, it does not explain the effect of the optional owner parameter or any pagination/permission 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?

Every sentence earns its place: the purpose, the return payload, and the usage rule. There is no filler and the key guidance is front-loaded.

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 listing tool with an output schema, the core use case and existence-check rule are well covered. The main gap is the unexplained owner parameter, which leaves the input model incomplete for an agent trying to understand all calling options.

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 schema has one parameter, owner, with 0% description coverage, and the tool description never mentions it. The agent is left with only the parameter name and default null to infer its meaning.

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 opens with a clear verb and resource: 'List the metrics this warehouse can answer for.' It also states what is returned and establishes that this is the existence-check tool, allowing an agent to distinguish it from get_metric and query_metric.

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 explicitly says 'Start here' and explains that a metric not on the list cannot be computed, which tells the agent to use this tool before querying or verifying metrics. It does not name sibling alternatives directly, but the when-to-use guidance is clear.

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