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 cutting/mutating action and mentions speed and access, but gives no information about side effects, reversibility, required permissions, billing implications, or state changes. The required npub billing parameter in the schema is not explained behaviorally.

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 description is a single compact sentence with no filler and front-loads the action. Its brevity is appropriate, though the cryptic phrasing trades clarity for conciseness.

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. But for a tool with required billing credentials, no annotations, and a potentially mutating action, the description is far too thin to inform safe and correct invocation.

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 67%, with npub and to_cell described but dpop_token undocumented. The description's 'one fresh cell of comb' loosely maps to to_cell, but it adds no format, range, or semantic detail beyond the schema, and it does not compensate for the undocumented parameter.

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 states an action and resource: 'Cut one fresh cell of comb.' It also names a comparison to the sibling beesknees_fly via 'slower than flying,' giving some differentiation. However, the metaphor is opaque and does not explain what digging accomplishes, what a cell of comb is, or what the tool returns.

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 only usage guidance is the comparative phrase 'slower than flying, and open to everyone after.' This hints at an alternative and an access condition but does not explicitly say when to use beesknees_dig versus beesknees_fly or other tools, nor does it state prerequisites.

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