sevennow_combo

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

With no annotations, the description carries full behavioral disclosure. It explains that the tool returns live pricing/availability, headline, and legal terms, and it discloses the quirk that the upstream may accept a plain item-discount promotion id but returns unnamed groups, steering the agent to the correct endpoint. It also states the 404 response for unknown IDs.

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?

Every sentence earns its place: purpose, example, return contents, ID provenance, alternative routing, and error behavior. The description is front-loaded with the core action and uses a concrete example to anchor understanding. Despite being long, it is dense and well-organized, not padded.

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 tool with no output schema, the description fully covers what the response contains, how to obtain required IDs, when to use an alternative endpoint, and error behavior. Nothing an agent needs to correctly invoke this tool is missing.

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?

The schema already provides 100% coverage with descriptions for both parameters, including provenance. The description adds an important edge-case caveat about the upstream accepting a plain item-discount promotion id, which gives the agent extra semantic understanding of promo_id beyond the schema. This lifts it slightly above the baseline.

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 ('Get') and resource ('one 7NOW bundle deal's pick-from groups'), and expands on what the result contains: pick-from groups, pick counts, eligible items with live pricing/availability, headline, and legal terms. The example makes the purpose tangible, and the contrast with sevennow_combos and sevennow_promotion helps distinguish it from siblings.

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 tells the agent where to obtain promo_id and store_id (from GET /7now/combos and GET /7now/stores). It also names an alternative endpoint for the specific case of a plain item-discount promotion id with unnamed groups, and documents the 404 behavior for unknown promo_id, so the agent knows when to route elsewhere.

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