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

Annotations already declare readOnlyHint=true, and the description reinforces it with a server-level guarantee ('this server never writes financial records'), which is stronger than the per-tool hint. It also discloses the returned fields (donor, date, method, batch, per-fund amounts), though it says nothing about pagination behavior beyond 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?

Front-loaded, single-sentence purpose followed by a short safety statement and the upstream API path; no filler or redundancy. Every clause carries information.

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 compensates by listing the return fields, and it covers scope, the optional fund filter, safety, and API provenance for a 5-parameter tool. Nothing an agent needs to call it correctly is missing.

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 five parameters are already documented, including the (fund) mapping for category_id and pagination defaults. The description's 'optionally for one fund' and 'per-fund amounts' largely restate that, so it adds little beyond the schema and the 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 and resource ('List giving transactions') plus its scope (between two dates, optionally one fund). An agent can distinguish it from sibling listing tools such as elvanto_list_financial_categories without opening any schema.

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?

Clearly conveys the required date-range context and that the fund filter is optional, which tells the agent when to supply category_id. It does not name alternatives or exclusions, but no sibling tool covers transactions, so there is little risk of misrouting.

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