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

With no annotations provided, the description carries the behavioral disclosure burden. It adds valuable context: the tool is free, requires proof of npub ownership, and treats credential presence as sensitive. It does not explicitly state side-effect freedom, but 'Report' and 'shows' strongly imply a read-only operation.

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 compact and front-loaded: the core purpose appears in the first sentence, and every subsequent sentence adds distinct value (service behavior, cost, auth requirement). No filler or redundant restatement of the schema.

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?

For a two-parameter read-only status tool with an output schema, the description covers the essential operational context: service-type differences, cost, and authentication. It could be slightly more complete by pointing to related credential-management siblings, but that is more of a usage-guideline refinement.

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 both parameters (patron_npub, dpop_token) are already well-documented in the input schema. The description adds only the contextual mention of proof-of-ownership, not new parameter-level semantics, so the baseline of 3 is appropriate.

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 opens with a specific verb and resource: 'Report a patron's credential readiness for this operator.' It then distinguishes patron-level status from sibling goodearth_get_operator_onboarding_status and explains service-specific meanings, leaving little ambiguity about what this tool does.

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 description gives clear context: it reports readiness, explains the two service categories (set-once vs OAuth2), and notes the proof-of-ownership requirement. However, it never explicitly references alternatives like goodearth_get_patron_credential_fields or states when not to use this tool, so exclusions are only implied.

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