list-metering-resources

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

With no annotations, the description must disclose behavioral traits. It mentions pagination and filtering, and implicitly indicates a read-only listing operation, but it doesn't describe response format, edge cases, rate limits, or what fields are returned. The sparse detail leaves significant behavioral ambiguity.

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 that immediately states the core action and key features. No fluff or redundancy; every word 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?

The tool is relatively simple (3 optional params, no output schema), but the description fails to explain what 'metering resources' are, what the response looks like, or how pagination/filtering behave in practice. It is insufficient for an agent to invoke with full confidence.

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 loosely aligns 'pagination' with page/page_size and 'filtering' with filter, but provides no specifics on formats, types (or that they are strings), or how to construct filter strings. The added value is minimal.

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 (list) and resource (metering resources), and mentions pagination and filtering. However, it doesn't clarify what constitutes a 'metering resource' nor explicitly differentiate from sibling metering tools like create-metering-job or get-metering-job.

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. It doesn't mention that this is the listing counterpart to metering job tools or provide exclusion criteria. The description only hints at functionality, not usage context.

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