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

Annotations already establish that this is a read-only, idempotent, non-destructive, closed-world operation. The description adds useful behavioral context by explaining that it returns the date, days left, tool recommendations, and occasion-specific retailer links, without contradicting the annotations.

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 description is front-loaded with the tool's purpose and then covers the occasion values, today default, and occasional retailer links. It is compact and every sentence adds information, though the first sentence is long and slightly overlaps the later retailer-link sentence.

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 an output schema available, the description does not need to fully document return structure, and it still explains both parameters and the special retailer-link behavior for certain occasions. It is complete enough for an agent to invoke the tool correctly, with only minor room to clarify the exact output shape or 'next' resolution logic.

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%, so the description must carry parameter meaning, and it does: it enumerates all occasion values including 'next' and explains that today is an ISO date defaulting to the server's date. This meaningfully compensates for the bare schema.

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 states the tool produces a holiday shopping plan with dates, days left, recommended Shoptegrity tools, and retailer deal links. It is specific about the resource and scope, and implicitly distinguishes itself from sibling tools by saying it recommends which Shoptegrity tools to use at each step rather than performing those checks itself.

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 gives clear context for when the guide applies: Black Friday, Small Business Saturday, Cyber Monday, Giving Tuesday, Christmas, or holiday gifts, with 'next' for the upcoming occasion. However, it does not explicitly say when not to use it or name sibling alternatives such as check_deal or verified_deals.

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