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

readOnlyHint=true already tells the agent this is a safe read, so the description's main added value is the REST endpoint (GET /api/v1/constituents/{constituent_id}/gifts) and the field list, which is useful because no output schema exists. It adds no notes on ordering, pagination behavior, permissions, or empty results.

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 sentences, front-loaded with what the tool returns before the endpoint reference. Nothing is wasted, though the raw endpoint string is arguably debug-oriented filler rather than agent-facing guidance.

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?

With no output schema, enumerating the returned gift fields is a real contribution and covers the main gap. However it says nothing about pagination semantics (the schema defines limit/offset but not how to page through a long giving history) or result ordering.

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% — limit, offset and constituent_id are all documented in the schema — so the schema carries the parameter burden. The description adds no syntax or filtering detail beyond what the schema already says, 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 states a specific verb+resource ('A constituent's giving history: every gift...') and enumerates the fields returned, which separates it from lgl_get_gift (single gift) and lgl_search_gifts (cross-constituent). It does not explicitly name those siblings as alternatives, so it stops 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?

There is no when-to-use guidance: nothing tells the agent to prefer this over lgl_search_gifts when it already has a constituent_id, and no prerequisites or exclusions are stated. The intended usage (fetch all gifts belonging to one constituent) is only implied by the phrase 'giving history'.

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