list_metrics

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

No annotations are provided, so the description carries the full burden. It is a zero-parameter list operation and 'Lista' implies a safe read, but the description never states that it is read-only or non-mutating, nor does it mention any auth or result-size behavior. It does add useful content context by naming the fields returned.

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 short sentences, zero waste, with the purpose front-loaded before the 'start here' guidance. Every clause earns its place.

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 zero-param discovery tool with an output schema already present, the description is nearly complete; it need not explain return values. A small gap is the absence of any note about ordering, volume, or whether results are paginated, but nothing critical to correct invocation is missing.

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 tool takes zero parameters, so there is nothing to disambiguate and the baseline is 4. The description correctly refrains from inventing parameters and instead describes the output shape.

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?

States a specific verb and resource ('Lista todas as métricas do contrato semântico') and enumerates what each entry carries (rótulo, descrição de negócio, dimensões aplicáveis). It does not explicitly name the siblings (describe_metric, query_metric), but its 'start here / complete vocabulary' framing does implicitly separate it as the discovery entry point.

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?

'Comece por aqui' gives clear positive guidance on when to reach for this tool first, positioning it as the vocabulary-discovery step before drilling into a specific metric. It stops short of naming the alternative siblings or stating when not to use it.

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