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

With no annotations, the description carries the full burden. It does add real traits not present in structured data: the call is free (no cost side effect) and it reaches out MCP-to-MCP to a third party. It omits auth/DPoP requirements (a dpop_token param exists), rate limits, and what happens when no request is on file, leaving significant behavioral gaps.

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?

Two short sentences, purpose front-loaded, no filler; 'Free.' efficiently flags the cost profile. The 'MCP-to-MCP' phrasing is mildly jargon-heavy but still informative.

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 enumerating pending/approved/rejected/provisioned in the description is redundant and return values need no further explanation. What is missing is the auth expectation for the undocumented dpop_token and the relationship to the adoption-request lifecycle, leaving the definition only minimally complete for a network-polling tool.

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 0% for both parameters. The phrase 'at a chosen Authority' does convey that authority_npub selects which Authority to query, but dpop_token is entirely unexplained in both schema and description, so the description does not 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?

States a specific verb and resource ('Check ... adoption-request status') plus scope ('this operator's ... at a chosen Authority'), which separates it from the write-side sibling beesknees_request_adoption. It never names an alternative explicitly, so sibling differentiation is implicit rather than stated.

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?

'Polls the Authority' and 'Free' imply this is a post-request, repeated-check call rather than a one-time action, which is usable guidance. However, there is no explicit when-to-use statement, no contrast with beesknees_request_adoption or beesknees_get_operator_onboarding_status, and no note on how often to poll.

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