get_usage_stats

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

With no annotations, the description carries full burden. It indicates a read operation with no side effects, but lacks details about caching, edge cases (e.g., no usage data), or how the billing period is defined. It 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, front-loaded sentence with no extraneous words. Every word carries meaning, and it efficiently communicates the tool's function.

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 zero parameters and presence of an output schema for return format, the description is nearly complete. It identifies the resource and time scope. Minor improvement could clarify behavior at the start of a billing period, but overall sufficient.

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?

No parameters exist, so the input schema is fully covered. The description correctly implies no configuration is needed, aligning with the zero-parameter schema. Baseline score 4 is appropriate as no param info is required.

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 returns recording-minute usage stats for the current billing period, with a specific verb and resource. It distinguishes from siblings like get_recording_summary, which deals with recordings rather than usage stats.

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 when current billing usage stats are needed, but does not provide explicit guidance on when to use this tool versus alternatives or mention any prerequisites, though the zero-parameter design reduces ambiguity.

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