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

With no annotations, the description carries the full burden and does well: it discloses the operator-only authorization requirement and the important non-retroactivity guarantee ('never rewrites history: every settlement records the beneficiary it actually paid at the time'). It omits rate limits and any confirmation/reversibility behavior, keeping it short of a 5.

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?

Purpose and the operator restriction are front-loaded, but the middle sentences ('It was a constant in the source...', 'A charity can be replaced, renamed, or rotate its wallet...') are rationale prose that do not help an agent invoke the tool correctly, diluting an otherwise compact definition.

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 return values need not be explained, and the description covers purpose, authorization, and the historical-settlement guarantee. The only real gap is the undocumented dpop_token parameter, which is minor given the 80% schema coverage.

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 description coverage is 80%, so the schema already documents name, npub, website, and lightning_address. The description echoes the three configurable fields but adds no syntax or format detail beyond the schema and says nothing about the dpop_token parameter; baseline 3 is appropriate.

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 (name/set) and resource (beneficiary/charity) with the exact fields it configures (name, website, Lightning address). It is distinguishable from siblings like beesknees_charity (read) and beesknees_pay_charity (pay), though it never names those siblings explicitly.

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 opening 'Operator:' plus the 'restricted, so the runtime requires the caller to be the operator, proven' clause effectively tells the agent who may invoke it. However, there is no explicit when-to-use vs when-not guidance or routing to the related siblings (beesknees_charity, beesknees_pay_charity), so usage is only implied.

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