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

Annotations already cover the safety profile (readOnlyHint, destructiveHint=false, openWorldHint), so the description only needs to add context – and it does: result ordering ('newest first'), the transaction type values (PDFGEN, PDFPREVIEW), and the underlying route (GET /list-transactions). It stops short of noting pagination/next_offset behavior, but that is documented in the schema.

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 sentences with the resource and field inventory front-loaded, followed by a short usage clause and the route. The field list is dense but earns its space since there is no output schema; only minor trimming possible.

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?

With no output schema, the description carries the return-value burden and does so by enumerating the returned fields, which is exactly what an agent needs. Ordering, field set, and route are covered; pagination is handled in the schema, so the gap is small.

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 limit and offset are already fully documented in the schema, including the next_offset chaining hint. The description adds nothing about either parameter, so the baseline 3 is the correct score.

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?

Clear verb+resource ('Recent generation transactions of the account') plus a full enumeration of returned fields (transaction_ref, type, execution time, credits used, etc.), so the agent knows exactly what comes back. It does not, however, differentiate itself from the sibling craftmypdf_query_template_usage, which plausibly overlaps on the 'what was billed' theme.

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?

'Use it to see what was billed' supplies a concrete use case, which is more than no guidance. But there is no when-not condition and no routing to the overlapping sibling query_template_usage, leaving the agent to infer which of the two to pick for usage/billing questions.

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