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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the read-only, live-data profile is covered. The description adds the shape of what comes back (promotion IDs, item groups, fixed-price offers), which is useful, but says nothing about pagination, result volume, or rate 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?

Two sentences, zero filler. The purpose comes first and the disambiguation against four siblings follows immediately.

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?

An output schema exists, so return values need not be explained, and the read-only/open-world annotations cover the safety profile. The description is complete for calling the tool; only operational details like result size or pagination are absent.

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 coverage is 100% and the lat/lon properties are thoroughly documented there as inert, so the schema is already doing the heavy lifting. The description only implies store scoping ('for a 7NOW store'), adding nothing beyond the 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?

Specific verb ('List') plus a precisely scoped resource ('bundle-combo deal records for a 7NOW store'), and it goes on to say what the records contain (promotion IDs and item groups behind fixed-price offers). An agent can distinguish this from sevennow_combo and sevennow_deals on the description alone.

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?

Explicitly routes the agent: sevennow_combo for one bundle, sevennow_deals for item deals, sevennow_offers/sevennow_promotion for campaigns. This is exactly the when-to-use-this-vs-alternatives guidance the dimension asks for.

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