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

No annotations are provided, so the description carries the full burden, and it does well: 'Check' signals a read-only operation, 'Free' discloses cost, and it explains the consequence of a zero balance (top-ups cannot be certified). It does not state auth/permission requirements, but the operational context is otherwise well disclosed.

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 core purpose is front-loaded in the first sentence, and every following sentence earns its place: the return value, the zero-balance consequence, the disambiguation from patron balance, and the cost. 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?

For a no-parameter read tool with an output schema, the description supplies everything needed: what it returns, why it matters, what to do at zero, and how it differs from patron balances. Nothing required to call it correctly 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 tool takes zero parameters, so the baseline of 4 applies. There is no parameter surface for the description to add meaning to, and it correctly does not invent any.

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 and resource ('Check this operator's tax balance at the Authority') and explicitly scopes it against the closest sibling concept by noting 'This is the operator's own funding — not a patron balance,' which separates it from beesknees_check_balance. An agent can identify the tool without opening the schema.

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 a clear condition and the follow-up action: 'When this balance reaches zero, patron top-ups cannot be certified and the operator must call purchase_credits.' This routes the agent to the right next step. It does not explicitly name the sibling to use for patron balances (beesknees_check_balance), so it stops short of full when/when-not/alternative coverage.

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