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

The readOnlyHint annotation already covers the safety profile, so the description's value-add is the payload disclosure: it enumerates nearly every returned field (contact, amounts, batch, designations, premiums, custom fields). That is genuinely useful behavior context given no output schema, though auth needs and not-found behavior are unstated.

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 plus an endpoint reference, with no filler. The long field enumeration is dense but earns its place because no output schema exists to describe the response.

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 simple one-param read with no output schema, enumerating the returned fields is exactly the missing context and it is provided. Only minor gaps remain, such as error/not-found behavior, which are not critical for correct invocation.

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 one parameter with 100% schema description coverage, so the schema already documents gift_id as a positive integer. The description adds nothing about the id's origin or format beyond the {giftId} path echo; 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 and resource with scope ('Fetch one gift in full'), and the endpoint mapping (GET /api/Gift/{giftId}) confirms it is a single-record read. This separates it from list-oriented siblings like virtuous_list_contact_gifts and cross-entity ones like virtuous_get_contact.

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 by 'one gift' plus a required gift_id; the agent can infer this is the detail lookup after a list/search. No explicit when-to-use, when-not, or named alternative (e.g. virtuous_list_contact_gifts) is given.

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