apollo_get_api_usage_stats

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

With no annotations, the description carries full burden. It discloses the need for a master API key and the error for non-master keys. The read-only nature is implied by 'View'. It could add more behavioral context, but the output schema likely covers the return structure.

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 consists of two concise sentences: the first states the purpose, the second adds a critical usage requirement. No extraneous words or redundancy.

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 parameters, the presence of an output schema, and the simple nature of the tool, the description is complete. It covers what the tool does, the authentication requirement, and the error case. No additional context seems necessary.

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 has no parameters and the schema description coverage is 100% (trivially). The description adds value by confirming no input is needed, serving as a baseline. No parameter information is missing.

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 'View your team's Apollo API usage and per-minute/hour/day rate limits across endpoints', using a specific verb and resource. It effectively distinguishes this tool from siblings, as none of the other 43 tools are for viewing API usage stats.

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 explicitly says when to use it (to view usage/rate limits) and provides a crucial prerequisite (requires a master API key) along with the consequence of using a non-master key (HTTP 403). However, it does not mention any alternative tools or when not to use it beyond the key restriction.

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