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

Annotations already declare readOnly/idempotent/non-destructive, so the bar is lower, and the description still adds real value: it discloses the privacy behavior that full card numbers are never returned and that donor contact data is suppressed unless include_contact is set, plus the newest-first ordering. It does not cover pagination or result-size behavior, but for a read-only list tool this is solid extra context.

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?

A single dense sentence that front-loads the resource and ordering, followed by the endpoint path. The enumerated field list is long but earns its place because there is no output schema; nothing is redundant.

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 enumerating the returned fields, and it flags the key privacy constraints. The remaining gap is that it does not state what an empty or limit-capped result looks like, but an agent has enough to call it correctly.

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% and both parameters are self-documented (limit range/default, include_contact off-by-default), so the baseline is 3. The description goes further by tying include_contact to concrete returned fields ('donor contact details are left out unless include_contact is set'), which clarifies the parameter's practical consequence rather than restating it.

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?

Names a specific verb+resource ('most recent donations/transactions') and states ordering ('newest first as Qgiv returns them'), which implicitly separates it from the date-range and after-id siblings. It stops short of naming an alternative explicitly, so it is clear but not fully differentiated from the other recent/list 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?

Use is implied by 'most recent' plus the limit-bounded endpoint, giving the agent a reasonable sense of when this fits (no date filtering, just the latest N). However there is no explicit when-to-use statement and no guidance on choosing it over qgiv_list_transactions_by_date or qgiv_list_transactions_after_id.

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