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 is covered. The description adds genuinely new behavioral context: results are a paged projection and sensitive sub-objects (payment instruments, addresses) are excluded from the response, which the agent would otherwise assume came back.

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?

Two short front-loaded sentences that lead with the payload scope and omissions; the endpoint reference is a minor redundancy but harmless. No wasted prose.

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 field enumeration and omission note usefully characterize the return value. However, for a paged list tool, the absence of any guidance on page numbering, sort behavior, or how to detect the last page leaves a real operational gap.

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%, so the description carries the full burden, yet it says nothing about the page parameter's numbering/default or the available sort values (id, started_on and their descending forms). "One page" is the only hint, leaving both parameters effectively undocumented for the agent.

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 ("Read one page of recurring donation amounts, schedules, status and supporter identity") that names the returned field set and explicitly notes what is omitted (payment instruments, addresses). The plural "list" form is clearly distinguishable from the sibling givecloud_get_recurring_profile.

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?

"Read one page" implies pagination and thus repeat calls, but the description never states when to use this list tool versus givecloud_get_recurring_profile, nor any prerequisites or filtering context. Usage is inferable from the plural name but not stated.

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