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

Annotations already declare readOnly, idempotent, non-destructive, open-world, so the safety profile is covered. The description adds valuable context beyond that: the integrity receipt, reconciliation, accessible text, the data accuracy contract about not inventing fields, and the attribution footer obligation. That is real added behavioral context. It does not cover rate limits, pagination, or failure modes, so it is not a 5.

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 front-loaded with the core purpose, which is good, but it is long and conflates output description, attribution rules, and a data-accuracy contract. Some of that is valuable, but the size is borderline for the amount of core information conveyed.

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 output schema exists and annotations cover safety, the description is complete enough: it covers input bounds, output format, verification contract, attribution obligations, and data-integrity rules. An agent has everything needed to call and interpret the result correctly.

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 have pattern, default, and description in the schema. The description only says 'optional start_date and end_date' with no added format or semantics beyond what the schema already provides, 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+resource pipeline: fetch Stripe balance transactions and account metadata, then return a verified PNG dashboard. It is clear what the tool produces. It does not, however, differentiate itself from sibling dashboards (e.g., stripe_connector, dashboard_render), so it falls short of the 5 tier.

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?

Usage is implied by the description of inputs and outputs but there is no explicit when-to-use guidance or distinction from stripe_connector/dashboard_render siblings. The attribution footer instruction is a usage rule, but not a selection rule.

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