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 status check via the cooldown wording, but says nothing about authentication, credit-billing implications (despite the npub param mentioning billing), rate limits, or 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?

A single short sentence with no filler. It is appropriately sized, though its brevity comes at the cost of substance rather than through efficient density.

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 spelled out, but for a 3-parameter, no-annotation tool the description is too thin. It leaves purpose, usage, auth/billing behavior, and one parameter undocumented.

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 67% and the description adds no parameter meaning whatsoever. It does not explain npub, match_id, or the undocumented dpop_token, 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 description is purely metaphorical ('where your bee stands, what it is carrying, when it may move again') and never states a verb or plainly names the resource, so an agent must infer this is a status/state query for its own bee. It does hint at three data points (position, cargo, cooldown), which is more than a tautology, but it does not clearly distinguish itself from siblings like beesknees_match_state or beesknees_session_status.

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 statement of when to use this tool, when not to, or which sibling to prefer for related state questions. The agent gets no routing guidance at all.

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