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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so safety is covered; the description adds genuinely new behavior: results come back 'newest first' and 'Test contributions are left out'. It stops short of describing pagination or volume expectations, but adds real value beyond the structured metadata.

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?

Three short clauses: what it returns, how to filter, then the exclusion rule and APIv4 source. Front-loaded with the payload fields and zero 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?

With 8 all-optional params, no output schema and annotations covering safety, the description supplies the missing pieces an agent needs: the shape of returned records, ordering, and the test-record exclusion. Only a hint about pagination/expected result volume is absent, and the schema's offset parameter largely covers that.

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 every parameter (limit, offset, status, date_from/date_to, contact_id, min_amount, financial_type) is already documented with formats and examples. The description only restates the filter set, adding no syntax or semantics beyond the schema. 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?

Specific verb+resource: 'Contributions (donations, membership dues, event fees)' with the returned fields enumerated and sort order stated. It is clearly distinguishable from siblings like civicrm_list_memberships, civicrm_list_participants and civicrm_record_contribution.

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 filter list ('Filter by contact, status, financial type, date range and minimum amount') implies when the tool applies, but there is no explicit when-not guidance or pointer to alternatives such as civicrm_query for compound/custom filtering. Usage must be inferred from the filters offered.

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