get_usage

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

With no annotations provided, the description carries the full burden, and it excels by explicitly stating that the call is free and does not consume quota. It also discloses what data is returned and warns about the hard rate-limit, giving the agent a complete behavioral picture.

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 compact and front-loaded with the tool's purpose and output contents, followed immediately by practical guidance. Every sentence serves a distinct function: what it reports, that it is free, and when to use it.

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?

For a zero-parameter read-only reporting tool with no output schema, the description is fully complete: it names the returned fields, confirms no quota impact, and provides clear usage timing. Nothing needed for correct invocation is missing.

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 input schema has zero parameters, so schema description coverage is vacuously 100% and there is nothing for the description to add about parameters. Per the baseline for 0-parameter tools, this is adequate.

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 states a specific verb ('Report') and a precise resource (the calling API key's current monthly quota), then enumerates the exact details returned. It is immediately distinguishable from the sibling tools, which concern financials and filings.

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 gives explicit context: check this tool before a large batch or long run to pace requests and avoid 429s. It does not name an alternative because none is relevant among the sibling tools, but it clearly explains when to use it.

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