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

While annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, the description adds behavioral context by explicitly stating that it returns credits and rate limit, and that it is 'Free' (likely meaning it does not consume quota). This goes beyond the annotations by clarifying the tool's side-effect-free nature in practical terms. No contradiction with annotations.

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 entire description is two short sentences, front-loaded with the most important information (credits and rate limit) followed by the 'Free' tag. Every word earns its place; there is no fluff, redundancy, or unnecessary detail. It is an exemplary model of conciseness for a simple status tool.

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 the tool's simplicity (no params, no output schema), the description adequately covers the return value at a high level (credits and rate limit) and the operational context ('this key', 'Free'). The only minor gap is the lack of detail on the exact response format or field names, but with no output schema and a clearly trivial resource, this is not a serious omission.

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 zero parameters, so the schema carries no burden. The description still adds meaning by referencing 'this key', which implicitly tells the agent that the tool operates on the current authentication context. This is useful context that the empty schema cannot provide, so the baseline for 0 params is met and slightly enhanced.

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 the resource ('this key') and the data returned ('credits left' and 'rate limit'), which clearly distinguishes it from all sibling tools that fetch tweets or users. However, it lacks an explicit verb like 'gets' or 'returns', relying on the title 'Balance' to imply the action. It is still specific enough for an agent to understand the tool's purpose.

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 offers no explicit guidance on when to use this tool versus alternatives, nor does it mention any exclusions. The phrase 'Free' hints that it can be called without cost, which implies a pre-flight check, but this is not stated. The intended use (checking credits/rate limit before other calls) is only implicit, not articulated.

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