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

No annotations are provided, so the description carries the full behavioral burden. It implies a read-only derivation but never states whether the call is safe/idempotent, requires authentication as the patron, or has side effects; nothing about the proof being deterministic or tied to an immutable snapshot is made explicit.

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?

A single front-loaded sentence with no filler; every clause carries meaning about what is generated and over what data.

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 described, and both required params are covered by the schema. However, with no annotations and no usage guidance, an agent still lacks context on when this proof tool is the right choice and what preconditions apply.

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 both parameters (npub, notarization_id) are documented there, so the baseline is 3. The description only reinforces the relationship between the patron's npub and the snapshot, adding no format, source, or lookup detail beyond the schema.

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 (generate) and resource (Merkle inclusion proof) plus the precise scope of the claim (patron's balance in a Bitcoin-notarized snapshot), which is far more specific than siblings like beesknees_list_notarizations or beesknees_notarize_ledger. It does not explicitly name which sibling to prefer instead, keeping it short of a 5.

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?

No indication of when to call this versus beesknees_check_proof_status, beesknees_list_notarizations, or beesknees_receive_npub_proof. Prerequisites (e.g. must the notarization already exist and be sealed?) are unstated.

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