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

With no annotations, the description carries the full burden and does disclose real behavior: the access restriction, that node_reachable:false blocks pay_out ('refuses on it'), and that covers_everything_owed is reported but not enforced. This is meaningful context beyond the schema, though it does not cover rate limits or exactly what the response looks like.

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?

It is reasonably sized, but the opening is a sentence fragment and the closing rationale ('refusing to pay one charity because a second is also owed helps neither of them') is explanatory prose that edges past what an agent needs to invoke the tool. Some sentences earn their place, some are atmosphere.

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?

An output schema exists, so field-level semantics need not be fully restated, yet the description still usefully clarifies what node_reachable and covers_everything_owed mean. The main gap is the undocumented dpop_token and the absence of a crisp purpose statement, but the behavioral picture is largely complete.

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 50%: npub is documented in the schema, but dpop_token has no description anywhere. The description adds no parameter meaning at all, so it fails to compensate for the undocumented half of the inputs.

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 frames the tool as an operator view of 'what the wallet can send, and what is owed out of it,' which conveys the resource but never states a clear verb (query/report) or explicitly distinguishes it from siblings like check_balance, check_authority_balance, or account_statement. The bulk of the text documents output fields rather than the tool's purpose, so an agent must infer it is a treasury-state read.

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?

It implies the caller must be the operator ('restricted, so the runtime requires the caller to be the operator, proven'), which is useful context, but it never says when to choose this over alternatives such as beesknees_check_balance or beesknees_payout_history. Usage is implied rather than stated.

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