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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description adds real value beyond them by declaring the result shape and explicitly scoping out donor/donation/amount data, though it says nothing about pagination or result limits.

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 clauses: purpose, field list, scope exclusion, endpoint. Front-loaded with the core action and zero filler sentences.

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 carries the burden of describing return contents and does so explicitly (field list plus Gift Aid / Donate flags). Pagination mechanics live in the schema, so nothing an agent needs to call this 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 75% (q, page, per_page documented; status enum undocumented). The description adds no parameter-level meaning, only field names of the returned records, so it neither compensates for the status gap nor improves on the schema.

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 the church's giving funds') and enumerates the returned fields (id, name, description, Gift Aid flags, Donate visibility, status). The 'Funds only: no donors, donations or amounts' clause draws a hard boundary that no sibling listing tool can confuse with.

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 negative scope ('Funds only: no donors, donations or amounts') usefully tells the agent what this tool will not return, but there is no explicit when-to-use trigger or named alternative. Usage is implied by the resource name rather than stated as a routing rule.

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