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

Annotations already declare readOnlyHint=true, destructiveHint=false, openWorldHint=true, so safety is covered. The description adds real value beyond that: the operation depends on a 'short-lived signed authorization' and requires user-approved signing, which the annotations don't convey. Not a 5 since auth failure behavior and rate limits aren't described.

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 tight sentences front-load the resource and immediately scope out the invoice siblings. Nearly every word earns its place; minor redundancy between the auth framing and the schema's parameter description.

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 single-parameter read tool with full annotation coverage and no output schema, the description covers purpose, scoping, and the authorization precondition adequately. An agent has enough to call it correctly, though return-shape expectations and the auth lifetime details remain unspecified.

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?

There is only one parameter and schema description coverage is 100%, and the schema itself spells out the confirm_account_access semantics (true only after user approved signing). The description reinforces this precondition but adds nothing the schema lacks, so baseline 3 applies.

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 (Read) and resource (the connected Nostr identity's Grynvault supporter, payment, and NIP-05 dashboard), and explicitly negates the invoice siblings by saying it 'does not create an invoice or change settlement.' An agent can distinguish this from create_grynvault_supporter_invoice / prepare_grynvault_* without opening schemas.

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 negation clause clearly carves out when NOT to use this (creating invoices, changing settlement), and the signed-authorization framing implies the required user approval precondition. It doesn't name a specific sibling alternative to route to, so it falls short of a full 5.

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