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

With readOnlyHint=true already covering the safety profile and no output schema present, the description carries useful weight by disclosing the shape of the returned payload (which fields come back). It does not mention error behavior for a missing id or rate limits, but the return-content disclosure is real added value.

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?

One front-loaded sentence that states scope and return fields, followed by the upstream API mapping. The endpoint reference is mildly redundant for an agent but is compact and potentially useful for tracing; no wasted prose.

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 annotations covering safety and no output schema, the description supplies the missing return-value picture. It stops short of noting not-found behavior or any expansion options, but nothing essential for calling it correctly is absent.

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?

Only one parameter, and the schema already documents it at 100% coverage ('Gift id (integer)', positive integer). The description's 'by id' adds no syntax, format, or constraint detail beyond the schema, so the 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 (get) and resource (gift) and scopes it to a single record by id, which cleanly separates it from the list_* and search_gifts siblings. It also enumerates the returned detail set (amount, deductible amount, dates, fund/campaign/appeal/event, payment type, acknowledgment template, tribute, custom fields), so an agent knows exactly what this fetch yields.

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 framing 'one gift by id' implies this is the single-record fetch and that bulk lookups belong to lgl_search_gifts or lgl_list_constituent_gifts, but no alternative is named and no when/when-not condition is stated. Usage is inferable rather than explicit.

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