wave_get_usage

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

No annotations are present, so the description carries full responsibility. It correctly indicates a read-only operation (retrieves usage data) but does not disclose any behavioral traits such as authentication requirements, rate limits, or side effects. The description is adequate but minimal.

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 sentence that is concise, front-loaded with the action ('Get current billing period usage'), and free of fluff. 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?

Given 2 optional parameters and no output schema, the description provides sufficient context about what data the tool returns (usage including streaming minutes, storage, bandwidth). It does not detail response format or pagination, but for a simple retrieval tool this is acceptable.

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 coverage is 100% with both parameters (period, breakdown) having enum descriptions. The description lists only the high-level metrics (streaming minutes, storage, bandwidth) but adds no meaning beyond the schema. Baseline score of 3 is appropriate when schema already documents parameters.

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 current billing period usage, specifying three concrete metrics (streaming minutes, storage, bandwidth). This verb-resource combination uniquely distinguishes it from sibling tools like wave_get_subscription (subscription details) and wave_get_stream_metrics (stream-level metrics).

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 implies usage for billing period queries but provides no explicit guidance on when to use this tool vs. alternatives like wave_get_subscription or wave_get_stream_metrics. No when-not-to-use or prerequisite information is given.

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