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

Annotations only flag idempotentHint and destructiveHint; the description adds substantial context beyond that: patch/merge semantics for `content` and `options`, the admin-role requirement on affected venues, the effect of `status` (hidden stops, active resumes), and a confirmation warning because changes hit members' upcoming gifts. This is exactly the extra behavioral detail the annotations don't carry.

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?

Four dense sentences, front-loaded with the core edit action, then merge rules, then permissions, then status/confirmation behavior. Every sentence carries information, though the status and confirmation points could be tightened.

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 complex mutation with nested objects and no output schema, the description covers mutation impact, auth, and update semantics, which is what an agent most needs. Return behavior is omitted but no output schema exists to require it, and a couple of unmentioned scalar fields are minor gaps.

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?

With only 29% schema description coverage, the description compensates well for the tricky parameters: it defines `giftId`'s source, explains the field-by-field merge of `content`/`options` (how to pass them), and clarifies `venueIds` role requirements. It says nothing about `message` or `orgId`, so it isn't fully compensating for the coverage gap.

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 opens with a specific verb+resource ("Edit a birthday gift") and anchors `giftId` to list_birthday_gifts, so an agent can separate it from create_birthday_gift and list_birthday_gifts. It stops short of an explicit "not for creating" exclusion, which keeps it at 4 rather than 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?

It states the operative conditions: send only the keys being edited, at least one field is required, and use `status` to stop/resume sending. It also advises confirming with the user first, which is actionable usage guidance. No sibling alternative is named for edge cases, so it falls short of a 5.

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