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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is covered structurally. The description adds real value beyond that by disclosing the fixed 30-day window, that only the calling key's data is visible (no cross-key access), and that the read is not billed — but it says nothing about result shape, aggregation, or whether history is retained beyond 30 days.

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?

Very short and front-loaded, but the embedded raw pricing JSON is pasted in verbatim and disrupts readability; a plain sentence ('reading your own usage is never billed') would carry the same meaning. The pricing block is also only marginally relevant to invoking the tool correctly.

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?

With zero parameters, no output schema, and full annotation coverage, the remaining burden is explaining what comes back — and the description does not describe the usage metrics, their granularity, or units. It is adequate to call the tool, but an agent cannot anticipate the response contents.

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?

The tool takes no parameters, so there is nothing for the description to disambiguate and the baseline of 4 applies. The time window, the one implicit 'input' an agent would otherwise ask about, is stated explicitly.

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 names a specific resource (usage) and scope (the calling key, last 30 days), which is enough for an agent to know it retrieves the caller's own consumption data. It stops short of saying what 'usage' actually contains (call counts, cost, rate-limit consumption), so the verb+resource is clear but the returned quantity is fuzzy.

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?

Implicit guidance only: the phrase 'for the calling key' signals this is the self-scoped variant, and the pricing note implies a billing/quota-checking use case. There is no explicit when-to-use, no mention of when a different tool would be better, and no stated prerequisite beyond holding a key.

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