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

With no annotations, the description carries the full burden and does so richly: it is explicitly free, distinguishes transient (warming_up) from permanent (misconfigured, quota_exceeded) failures, states that paid tools fail in some states while free tools remain available, names the upstream provider behavior (Neon HTTP 402), and discloses bootstrap/auth prerequisites. That is far more behavioral context than annotations would typically convey.

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?

Front-loaded with the core purpose and a key constraint ("Free") in the first two sentences, then a clean, scannable state list. Each state entry is distinct and earns its place by telling the agent what the state means and whether retrying helps.

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 format need not be explained, and the description instead explains the meaning of every state and the required follow-up action. For a readiness/diagnostic tool with one optional parameter, nothing an agent needs in order to call it and act on the result is missing.

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 100% and the single optional parameter (patron_npub) is fully documented in the schema, so the schema does the heavy lifting. The top-level description never references the parameter or its upstream_oauth side effect, so it adds nothing beyond the schema — the baseline 3 for high coverage is correct.

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 and resource — "Check operator readiness" and returns the operator lifecycle state — so an agent knows exactly what it does. However, it never distinguishes itself from near-name siblings like weather_get_operator_onboarding_status, weather_service_status, or weather_adoption_status, which an agent would have to disambiguate on its own.

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 strong post-call guidance embedded in each lifecycle state ("Retry", "Call register_operator first", "retrying does NOT help"), which effectively tells the agent what action follows each result. But it gives no explicit when-to-use-this-vs-alternatives routing against the many status siblings, so selection guidance is implied rather than stated.

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