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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description goes beyond that by enumerating the returned statuses and their meaning (idea = not bought yet, bought = needs wrapping, wrapped, done) and the budget fields, which is genuinely useful behavioral context given no output schema exists.

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 with the core action first, followed by the return-value detail. The parenthetical status legend is dense but each clause carries information; nothing is redundant filler.

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 no output schema, the description supplies the return shape (statuses, budget/remaining/over_budget_by, from_wishlist) that would otherwise be unknown. Minor gaps remain on error behavior for an unknown person_id and on whether household sharing affects results.

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 0% for the single person_id parameter. The description clarifies that the ID identifies the one person whose gifts are shown, but it does not state the expected format (uuid in the schema) or whether it is a person record rather than a user ID. It adds meaning but leaves a 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?

States a specific verb and resource ('Shows the gifts ... has planned or bought for one person on their gift list') and scopes it to the signed-in person plus household. The scope is clear enough to separate it from list-level tools like get_my_gift_lists, though no sibling is named explicitly.

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 implied: read this when you want one person's planned/bought gifts rather than the account's lists. There is no explicit when-to-use vs. when-not guidance, no mention of find_gifts or get_person_overview as alternatives, and no stated prerequisites.

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