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

With no annotations present, the description carries the full transparency burden. It discloses that the tool is free and consumes no credits, that proof of npub ownership is required, and that its purpose is to prevent statement-scraping. It does not explicitly state read-only status, but 'Returns...' plus the cost disclosure make the safety profile reasonably clear.

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 first sentence states the core action, the second lists return contents, the third provides a key semantic distinction, and the fourth covers cost and authentication. Every sentence earns its place with no filler.

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?

Given the tool's moderate complexity, the presence of an output schema, and fully documented parameters, the description provides enough context to invoke the tool correctly. It covers purpose, return content, cost, and auth requirements. It is missing only explicit read-only confirmation and explicit routing guidance to alternatives.

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%, so the baseline is 3; the schema already thoroughly documents npub, dpop_token, and days. The description adds some context by framing dpop_token as 'proof of npub ownership' and implying days affects 'recent daily usage logs,' but it does not materially extend parameter semantics beyond the schema.

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 starts with a specific verb-object pair, 'Generate a patron's account statement,' and then enumerates the exact contents: purchase history, active credit tranches, per-tool usage breakdown, and daily usage logs. It also distinguishes itself from the operator's Authority tax balance, which is especially useful given the sibling tool roastify_check_authority_balance.

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 intended use is implied by the description, but it never explicitly states when to use this tool versus alternatives. It includes a 'not the operator's Authority tax balance' clarification, but it does not name a sibling alternative or give an explicit when-to-use / when-not-to-use rule.

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