get_usage

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

Discloses that it returns usage data for the current month and includes fields like overage info. No annotations exist, so description carries full behavioral burden. Lacks details on authentication, rate limits, or side effects, but as a read-only query with no parameters, it is adequate.

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 efficient sentences: first defines output, second provides usage advice. No wasted words.

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?

Describes output fields in plain language despite no output schema. Could be more precise about data format, but sufficient for agent to understand return value.

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 (0 params, 100% schema coverage). Baseline of 4 applies as the description need not compensate for parameter documentation.

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?

Clearly states it reports account plan and execution usage for the current calendar month, listing specific metrics (used, included_executions, remaining, overage allowed). Distinct from sibling tools like get_execution which likely handle individual executions.

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?

Explicitly advises checking before large batches to avoid hitting a hard quota, providing a clear use case. Does not specify when not to use, but context is sufficient.

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