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

With no annotations supplied, the description carries the full behavioral burden and does so richly: it distinguishes transient ('warming_up') from permanent ('misconfigured', 'quota_exceeded') failures, states explicitly when retrying will not help, names the provider and HTTP 402 semantics, and clarifies that free tools remain available while paid tools fail. This is far beyond what any structured field conveys.

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?

Purpose is front-loaded and the lifecycle states are cleanly bulleted, so the length is justified by genuine state complexity rather than padding. The stray 'Free.' fragment is slightly awkward, but overall the structure is efficient and scannable.

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-value documentation is not required, yet the description still enumerates every lifecycle state and its implications. Combined with the fully-covered schema, an agent has everything needed to invoke and interpret this tool correctly.

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?

The single parameter patron_npub is fully documented in the schema (100% coverage) including its upstream_oauth side effect, so the schema does the heavy lifting. The description adds no parameter-level meaning at all, which is the correct baseline 3 given complete schema coverage.

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 a specific verb+resource ('Check operator readiness', 'operator lifecycle state') that an agent can act on immediately. It is clear what the tool does, but it never names or contrasts against related siblings such as goodearth_get_operator_onboarding_status or goodearth_service_status, so the agent must infer the boundary itself.

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?

Usage is implied rather than stated: the per-state next-actions ('Retry', 'Proceed with tool calls', 'Call register_operator first', 'retrying does not help') effectively tell the agent what to do once it has called the tool, and 'Free' hints this is a cheap preflight. However, there is no explicit when-to-call-this-vs-alternatives guidance relative to the many sibling status/balance tools.

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