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

With no annotations, the description carries the full behavioral burden. It does disclose one useful trait — the call is free despite the sibling tools' credit billing — but says nothing about whether it is read-only, what auth is actually needed (the schema's npub note mentions credit billing, which conflicts with 'free'), or any side effects.

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 definition is short and the functional hint ('Free on purpose') is front-loaded, but the second sentence is philosophical rationale rather than information an agent can act on, so roughly half the text does not earn its place.

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, but for a tool in a credit-billing ecosystem the description omits what 'charity share' means, how the destination relates to set_charity, and the auth/cost model. It is too thin for the surrounding complexity.

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 only 50%: npub is documented (and oddly labeled 'Required' while the schema lists zero required params) and dpop_token is completely undocumented. The description adds no parameter meaning at all, so it fails to compensate for the coverage gap.

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 phrase 'Who the charity share goes to, and where to check them' conveys the subject matter but uses no clear verb and never says outright that this is a read/query of the current charity destination. It is distinguishable from beesknees_set_charity and beesknees_pay_charity only by inference, not by any explicit statement.

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?

There is no when-to-use guidance, no prerequisites, and no mention of the obvious alternatives (set_charity to change the destination, pay_charity to send funds). The second paragraph discusses cost philosophy but gives the agent nothing actionable about when to invoke this tool.

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