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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), so the description's real value-adds are the privacy behaviors: contact details are gated behind include_contact, and card data is deliberately reduced to the last four digits. It also discloses that the read is performed via POST /reporting/transactions/{id}, a non-obvious detail for a read-only tool. A bit more on rate limits or pagination would push this higher.

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 dense, front-loaded sentence that names the payload first, then the two behavioral caveats, then the endpoint path. Every clause earns its place; the only minor cost is the somewhat breathless field list.

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?

There is no output schema, so the description does the compensatory work by enumerating the returned sections and the contact/card masking rules. Combined with the endpoint disclosure, an agent has enough to call it correctly, though nothing says what an unknown id or empty result looks like.

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 coverage is 100%, so the baseline is 3, but the description adds meaning beyond the schema: it explains what include_contact actually unlocks (contact details) and what is returned without it, plus the card-number truncation behavior tied to the response rather than the flag itself.

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 precise verb+resource (fetch one transaction by id) and enumerates the payload scope: donation lines, fund/restriction, dedication, custom-field answers, event packages, registrations, refunds. The singular 'one transaction' clearly separates it from the many list_* siblings such as qgiv_list_recent_transactions and qgiv_list_transactions_by_date.

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 rather than stated: the singular 'one transaction' plus the required id suggests fetch-by-known-id versus the list siblings, but no alternative tool is named and no 'use this when...' condition is given. Adequate but leaves the routing decision to inference.

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