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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so safety is covered. The description adds genuinely new context: the required Cotlet API key scope and the exact shape of each returned row (including thank-you status). It stops short of noting pagination or result limits.

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?

The first sentence already lists purchaser, order info, cash-fund contributions and thank-you status, then the next two sentences restate the same fields ('the guest who bought each physical gift, the quantity and order info... Each row says whether a thank-you was sent'). This redundancy costs space without adding information.

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, the description usefully explains what the rows contain and how they map to the Registry 'Track' tab, and it flags the auth requirement. For a two-parameter read tool with full schema coverage and clear annotations, this is largely complete, missing only result-volume/pagination behavior.

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%: 'since' is documented as a date filter and 'event_id' points to list_events. The description adds no parameter-level detail 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 clear verb+resource (list received gifts) and enumerates the payload: purchaser, quantity, order info, cash-fund contributions, thank-you status. It does not, however, distinguish itself from the close sibling joy_list_registry_gifts, leaving the agent to infer whether 'received gifts' differs from 'registry gifts'.

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?

No when-to-use or when-not-to-use guidance is given, and the very similar sibling joy_list_registry_gifts is never mentioned. The only contextual statement is an auth requirement (Cotlet API key), which is a prerequisite, not usage direction.

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