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

With readOnlyHint=true already covering the safety profile, the description adds useful context: the exact fields returned and the default sort order ("newest first"), which clarifies behavior the annotations don't cover. It still says nothing about pagination, result limits, or how the sort defaults interact with the sort parameters.

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 compact sentences that front-load the core verb and resource, followed by a useful listing of returned fields. The trailing API endpoint note is arguably redundant but short and unobtrusive.

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?

No output schema exists, so the description's enumeration of returned fields partially compensates by telling the agent what to expect. Combined with the readOnly annotation and full schema coverage, this is largely sufficient for a straightforward read/list tool, though pagination expectations remain unstated.

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%, so all four parameters (account_id, sort_column, sort_direction, current_page) are already documented in the schema. The description's "newest first by default" adds slight meaning to the sort behavior, but overall the schema does the heavy lifting, 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?

States a specific verb and resource ("List one account's donations") and enumerates the returned fields (amount, date, fund, campaign, purpose, status, payments), which clearly distinguishes it from the singular neon_get_donation sibling. It does not explicitly name competing list/search siblings, so it falls 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 phrase "one account's donations" implies the usage context (retrieve donations scoped to a single account) and "newest first by default" hints at default ordering behavior. However, there is no explicit when-to-use guidance or exclusion pointing to alternatives such as neon_get_donation for a single record or neon_search for cross-account queries.

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