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

Annotations already declare readOnlyHint=true, so the safety profile is covered. The description goes further by enumerating the returned payload (amount, date, fund, campaign, purpose, source, tribute, soft-credit solicitor, payments, status), which is genuinely useful since no output schema exists. It omits error/not-found behavior and auth requirements, keeping it short of a 5.

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 that are front-loaded with the action and resource, then the payload contents. The trailing 'Neon: GET /donations/{id}' is mild redundancy with the tool name and schema, but overall there is little waste.

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 single-parameter read tool with readOnlyHint and no output schema, the definition supplies the resource scope, the required id semantics, and a preview of returned fields. Only edge-case behavior (not found, permissions) is missing, which is acceptable at this complexity.

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% and there is a single required parameter, so the schema already documents donation_id fully. The description's 'GET /donations/{id}' confirms the id path semantics but adds no format, constraint, or sourcing detail 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?

States a specific verb (Fetch) and resource (one donation), and the singular phrasing plus the enumerated payload distinguishes it from sibling list tools like neon_list_account_donations and the broader neon_search. It does not explicitly name a sibling to route against, but the singleton scope is unambiguous.

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 'one donation' phrasing and the required donation_id imply usage (fetch a known record), but there is no explicit statement of when to prefer this over neon_search or neon_list_account_donations, nor any prerequisites. Usage is implied rather than stated.

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