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

'Read only' merely restates readOnlyHint=true, so it earns no credit; the useful addition is the underlying GET /transactions endpoint mapping. It does not disclose pagination/limit behavior, ordering defaults, or result shape beyond what the schema already provides, and with annotations present the bar is lower.

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 that are front-loaded with the core purpose and end with the API mapping; every clause (subtypes, designations, filters, read-only) carries information 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?

For an 11-parameter, all-optional list tool with full schema coverage and no output schema, the description covers purpose, entity scope, and filter capabilities adequately. It could say more about pagination/ordering behavior, but the schema already documents skip/take/order_by/order_direction.

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 all 11 parameters are already documented with meaningful descriptions in the schema. The description's filter list mirrors the schema without adding format, syntax, or interaction details, so the baseline of 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 (List) plus resource (transactions) and enumerates the transaction subtypes covered (donations, pledges, pledge payments, recurring donations and payments) as well as the attached designations. This clearly separates it from the singular bloomerang_get_transaction and from the list_* sibling tools.

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 spells out the available filter dimensions (constituent, amount range, type, last-modified date), which implies when the tool is useful, and 'Read only' signals safe use. However, it never explicitly says when to use this instead of bloomerang_get_transaction or the other list tools, so the routing is left to inference.

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