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

The only behavioral claim is 'Read only,' which merely restates the readOnlyHint=true annotation already present, so it adds no new information. The GET /transactions endpoint mapping is mildly useful context, but the description says nothing about pagination limits, default sort behavior, or result envelope.

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?

One tight sentence with the core purpose front-loaded, followed by short filter and endpoint notes. Slightly padded by the redundant 'Read only' clause that duplicates annotations, but overall efficient.

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 list tool with no output schema and only a readOnlyHint annotation, the description is adequate but leaves gaps an agent would want: pagination behavior (take max 50, skip), default ordering, and whether results include designation detail. Coverage of the filter surface compensates partially.

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 fully documents all 11 parameters — the baseline is 3. The description's filter mentions (constituent, amount range, type, last-modified) loosely map to parameters but add no syntax, defaults, or semantics beyond what the schema already provides.

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) and resource (transactions/gifts) and enumerates the subtypes covered — donations, pledges, pledge payments, recurring donations — plus the associated designations. This clearly separates it from the sibling bloomerang_get_transaction (single record) and from the create_* write 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?

It lists the available filter axes (constituent, amount range, type, last-modified date), which implies when the tool is useful, but gives no explicit when-to-use/when-not guidance or named alternative for retrieving a single gift. Usage is inferable rather than stated.

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