get-billing

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

Annotations already declare readOnlyHint=true; description adds critical context about v2-only requirement and 501 error on v1 API. Also mentions record capping and pagination, enhancing transparency beyond annotations.

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 well-structured sentences: first states primary action and scope, second adds version warning and parameter guidance. No redundant information; front-loaded with key purpose.

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?

Lacks description of output format (e.g., what fields are returned per bucket). While pagination and time window are covered, the response structure is omitted, leaving some ambiguity for agent understanding.

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 good descriptions. The tool description adds value by explaining mutual exclusivity of lastN and startTime/endTime, and clarifies pagination cursor usage, making parameter semantics clearer.

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 'time-bucketed Runpod spend history' and explains the aggregation vs breakdown by resource type. It uses specific verbs and differentiates from siblings as the only billing-related tool.

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?

Covers key usage details: v2-only with 501 on v1, pagination via limit/cursor, and time window narrowing via startTime/endTime or lastN. Does not explicitly state when not to use, but alternatives are absent.

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