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

Annotations already declare readOnlyHint=true, so the safe-read profile is covered. The description adds nothing beyond that – no note on pagination behavior, result ordering, or what happens for a constituent with no gifts. Adequate but thin for a read-only list operation.

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, front-loading the resource and return fields, with the REST endpoint appended as a lookup aid. No filler; slightly denser than the minimum but every element is relevant.

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 usefully enumerates the fields returned, and pagination is fully handled in the input schema. Missing only the routing relationship to sibling gift tools (search_gifts, get_gift).

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%, with limit, offset and constituent_id all documented in-schema including defaults and next_item paging guidance, so the baseline is 3. The description adds no parameter-level meaning beyond the schema (the field list is output semantics, not input semantics).

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+resource, 'a constituent's giving history', and enumerates the returned gift attributes (amount, date, gift type, fund, campaign, appeal, event, payment type). It is clearly scoped to a single constituent, but never names the sibling lgl_search_gifts, so an agent must infer the boundary between the two gift-listing tools.

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: it reads like the tool to call when you already have a constituent_id and want their gifts. There is no explicit when-to-use, no contrast with lgl_search_gifts, and no stated prerequisites such as whether the constituent must exist or be accessible.

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