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 still adds real context beyond them: the exclusion of archived lists, inclusion of household-shared lists, and the domain model that idea = not bought, bought = bought but unwrapped, then wrapped, then done — a non-obvious lifecycle the agent could not infer from annotations or schema.

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?

Purpose is front-loaded in the opening clause, and each block (returned fields, status lifecycle, example queries) earns its place because no output schema exists. However, the field enumeration is packed into one long run-on sentence, making it harder to scan than a short bulleted structure would be.

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 must carry the return shape, and it does so field by field (budget, planned total, remaining_budget, over_budget_by, status counts and amounts, wishlist/own-idea counts). Remaining gaps are minor for a read-only, zero-required-parameter report: list ordering, and what the response looks like when the person has no current lists.

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% for the single optional 'list' parameter, and the schema already documents it as a name filter with an example. The description never mentions the filter or how the report changes when it is supplied. With the schema doing the work, the baseline of 3 applies and no extra meaning is added.

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 names a specific artifact ('a status report for the signed-in person's current (not archived) gift lists') and enumerates the per-list and per-person figures it returns (gift counts by status, over budget, wishlist_gift_count). The scope qualifier 'current (not archived)' and 'including lists shared by their household' separates it from the sibling list/create/delete tools, so an agent can identify it without opening the schema.

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?

Three concrete example questions ('how am I doing on Christmas shopping?', 'who am I over budget on?', 'how many gifts do I still need to buy?') give the agent a clear trigger. There is no explicit when-not guidance or named alternative (e.g. get_person_overview or get_my_wishlist) for single-person or single-list lookups, which keeps it from a 5.

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