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

Annotations already declare readOnlyHint=true, so the safety profile is covered and the bar is lower. The description adds real value by listing the fields returned (amount, date, fund, campaign, tribute, soft-credit solicitor, payments, status) and the underlying endpoint, which is useful since no output schema exists.

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?

A single front-loaded sentence: verb+resource first, then the field inventory and endpoint. Nothing is wasted, though the long field list and the 'Neon: GET /donations/{id}' suffix are slightly dense for one sentence.

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 one-parameter read tool with no output schema, the description compensates by enumerating the return fields, which is the main thing an agent would otherwise lack. It stops short of describing error behavior for a missing or unknown donation_id.

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?

There is a single parameter with 100% schema description coverage, so the schema already documents donation_id. The description adds no format, ID-source, or validation semantics beyond what the schema states, making the baseline 3 appropriate.

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 ('Fetch one donation') and enumerates the returned fields, so the agent immediately understands this is single-record retrieval by ID rather than a list. It does not explicitly name the sibling it contrasts with (e.g. neon_list_account_donations), so differentiation is implicit rather than stated.

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: the mention of 'one donation' and the endpoint 'GET /donations/{id}' signal that a donation_id is required for point lookup. There is no explicit when-to-use, no when-not-to-use, and no pointer to neon_list_account_donations or neon_search for bulk retrieval.

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