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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description still adds real value by characterizing the output as illustrative etiquette guidance rather than advice, and by explicitly ruling out a money-transfer behavior, which preempts a plausible misinterpretation of a 'cash gift' tool.

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?

Three short sentences: what is returned (with units), what the numbers mean, and what the tool does not do. The return-value statement is front-loaded and nothing is redundant or padding.

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?

There is no output schema, but the description supplies the essential return shape (low/typical/high range in USD), which is the main thing an agent needs. It stops short of describing the response envelope or any caveats about which relationship/party combinations are supported, but it is complete enough 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?

Schema description coverage is 100%, with enums documented for party and travel and an explanation that an absent relationship value returns the available options. The description names the same input dimensions but adds no formats, defaults, or interaction rules beyond the schema, so the baseline of 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 precise verb and resource: returns an illustrative low/typical/high cash wedding gift range in USD, and enumerates the four inputs that drive it (relationship, party, travel, wedding-party role). That level of specificity separates it from the other estimate-style siblings such as get_budget_estimate, get_alcohol_estimate, and get_who_pays_split without needing to name them.

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 description frames the output as 'US etiquette conventions, not obligations' and clarifies it 'does not transfer money,' which implies a consultative/advisory use case, but it never states when to call this versus alternatives like get_who_pays_split or get_budget_estimate, nor any prerequisites. Usage is inferable but not explicit.

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