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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds one behavioral signal beyond that: each returned bundle carries its underlying promotion id, which hints at the response shape and the link to sevennow_promotion. It says nothing about rate limits, empty-result behavior, or store-id validity.

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?

A single front-loaded sentence with zero filler; every clause earns its place. It is terse almost to a fault, but nothing is wasted.

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 one-required-parameter list tool with an output schema present, the description needn't explain return values. It correctly conveys the per-store scope and notes the embedded promotion id; the remaining gap is the absence of routing guidance against the singular sevennow_combo sibling.

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% and the schema itself is unusually informative (the lat/lon parameters are explicitly documented as inert, with measurement provenance). The description adds no parameter detail, so the baseline 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?

The description states a specific resource (bundle deals/combos) and scopes it to a single 7NOW store, so an agent can tell what it returns. However it never names or contrasts the very similar sibling sevennow_combo (singular) or sevennow_deals/sevennow_offers, leaving sibling differentiation to inference.

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?

There is no statement of when to use this tool versus sevennow_combo, sevennow_deals, sevennow_offers, or sevennow_promotion. The only implied context is 'per store', which is derivable from the required store_id parameter.

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