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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile needs no restating. The description adds genuine behavior beyond that: pagination scope ('one page'), the exact set of returned fields, the fields deliberately omitted, and that date filters are exclusive and UTC. It stops short of return shape, page size, or ordering defaults.

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 tight sentences, front-loaded with what is returned, then what is omitted, then filter semantics. The trailing raw endpoint 'GET /admin/api/v3/contributions' is low-value for an agent but costs little.

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 usefully enumerates returned and omitted fields, which is the right compensation. However, with 8 parameters at 0% schema coverage, four filter flags remain unexplained, and page size / default sort behavior is unstated — meaningful gaps for a paginated list tool.

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 0% across 8 parameters, so the description must carry the load and largely does not. Only the date boundary semantics are clarified ('Date filters are exclusive and UTC'); sort, page, onetime/recurring, and the ambiguous initial_recurring vs one_time_and_initial_recurring flags are left entirely undocumented in both schema and description.

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?

The description names a specific verb and resource ('Read one page of contribution amounts, status, supporter identity and selected line items') and enumerates what the record contains and omits. It implicitly separates itself from givecloud_get_contribution (singular) and givecloud_list_recurring_profiles via 'one page' and the contribution-specific field list, but never names a sibling explicitly.

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 only implied: 'Read one page' suggests a paginated list endpoint and the exclusion sentence hints at when to look elsewhere for payment instruments or addresses. There is no explicit statement of when to pick this over givecloud_get_contribution for a single record, nor any prerequisite or rate-limit guidance.

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