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

With no annotations provided, the description carries the full burden and handles it well by disclosing the 1 api_sat cost per call and the debit_or_deny proof verification before cost is incurred. It also reveals the output composition including hero, metrics cards, health gauge, tranche table, and usage breakdown. It doesn't mention side effects or failure modes, but generation tools are reasonably covered.

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, starting with the core action and then efficiently covering the output format, cost, and proof verification. Every sentence contributes useful information and there is no redundant or filler content.

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?

The description covers the tool's purpose, output format, costing, and authentication proof flow, and an output schema exists to define return values. It is nearly complete, though it could have been slightly more explicit about when an agent should prefer this over the plain account_statement tool.

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 schema already fully documents npub, dpop_token, and days. The description adds no additional parameter-level meaning beyond reiterating that it renders the same statement data, which is enough to maintain the baseline without needing further compensation.

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: generating a visual SVG infographic of an account statement. It also distinguishes this tool from the sibling taxsort_account_statement by noting it returns the same data rendered as a dark-themed SVG graphic, so an agent can tell them apart.

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 names taxsort_account_statement as the source of the same data and clarifies that this tool renders it as an SVG infographic. This gives clear context for choosing between raw data and visual presentation, though it does not explicitly spell out when not to use this tool or provide exclusion conditions.

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