Check the remaining request budget

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

No annotations are provided, so the description carries the full burden. It discloses that the call costs nothing, that the endpoint is exempt from the budget it reports, that the window is shared across all provider hosts, and that numbers are identical regardless of provider. These are critical behavioral facts an agent could not infer otherwise.

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 cost and usage condition, then the return details, then the shared-window caveat. Dense but every clause carries necessary information; no filler.

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?

Complete for a simple single-optional-parameter read tool with no output schema. It covers cost, when to call, what is returned, the shared-window semantics, key presence, and where to raise the limit.

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 coverage is 100% and the schema already documents the provider parameter's enum and role. The description adds the non-obvious insight that the parameter value doesn't change the output because the budget is one shared window. That's meaningful beyond the schema but the parameter itself needs no further explanation.

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?

States a specific verb+resource ('check ... budget') and explains exactly what is returned: limit, remaining, reset time, key presence, and how to raise the limit. This is far more than a restatement of the name and clearly distinguishes it from siblings like orient or get_snapshot.

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?

Gives explicit conditions: 'call it before any loop of more than a handful of requests.' This is concrete and actionable guidance about when to use the tool that no sibling provides.

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