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

Annotations already establish readOnlyHint=true, so the safety profile is covered. The description adds a genuinely behavior-relevant fact not present in structured fields: results are returned newest first by default, plus it discloses the underlying Neon endpoint (GET /accounts/{id}/donations), which helps predict pagination/response shape.

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 tight sentences, zero filler, with the core purpose and default ordering front-loaded before the optional endpoint note.

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?

For a read-only list tool with no output schema, the description compensates well by naming the returned fields (amount, date, fund, campaign, purpose, status, payments) and the default sort, while the schema fully documents pagination and sort parameters. Minor residual gaps: no statement of pagination depth or result caps.

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%, so the baseline is 3. The description adds meaning beyond the schema by stating the default ordering ('newest first'), which clarifies the effective values of sort_column/sort_direction when they are omitted, something the enum-only schema does not specify.

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 with scope ('List one account's donations') and enumerates the returned fields, so an agent can tell it apart from neon_get_donation (single) and neon_list_accounts (different resource). It does not explicitly name a sibling alternative, keeping it just short of a 5.

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 account-scoped phrasing implicitly signals when to use this list endpoint versus a single-record get or a cross-account search, but there is no explicit when-to-use, prerequisite, or named alternative. Usage must be inferred rather than read.

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