usage_me_overview

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

Discloses that it returns JWT-authenticated user data, billing snapshot, and metrics, and specifies request traffic exclusions. Without annotations, the description adequately communicates the tool's behavior, though rate limits or permissions are not addressed.

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?

Three sentences, front-loaded with the main purpose, no redundant words. Efficiently communicates essential information.

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 no output schema, the description covers key return elements and constraints. However, it does not explain the structure of the billing snapshot or metrics, and the range parameter presets are left ambiguous in the schema.

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 covers 100% of parameters with descriptions. The description adds that range defaults to billing period and confirms from/to are for custom ranges, but does not significantly enhance understanding beyond the schema.

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 the tool retrieves the current user's usage overview with billing snapshot and request/credit metrics. Does not explicitly differentiate from sibling tools like usage_me_timeseries but is specific enough.

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?

Provides context on scope (selected UTC time range, excludes certain endpoints) but lacks explicit guidance on when to use this tool versus alternative usage-related tools. No mention of prerequisites or trade-offs.

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