Promotions

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

The annotations already establish a safe, read-only, idempotent operation, while the description adds useful result behavior: flash sales include end times, product sections expose downstream `collection_id` values, and slugs can be found in site links. It does not cover freshness or empty-page behavior, but those omissions are modest for this simple discovery tool.

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 front-loads the tool's purpose and then gives two compact integration details. Every phrase contributes either scope, output context, or invocation guidance without repetition.

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 read-only tool with one optional, fully documented parameter, the description and schema together provide enough information to select a page, understand the promotional content, and continue to `ss_collection`. Although there is no output schema, the description adequately summarizes the important returned elements and identifiers.

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 fully documents the optional `page` parameter, including its default, supported patterns, and examples. The statement that slugs appear in site links adds practical guidance for discovering the `<slug>` values needed to invoke non-default pages.

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 uses a specific verb and resource—showing what Snapp! Shop is promoting—and concretely identifies flash sales, carousels, campaign pages, and top products. The `collection_id` handoff to `ss_collection` also helps distinguish its promotional-discovery role from the sibling collection tool.

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?

It provides clear context for browsing promotions and directs the agent to `ss_collection` when it needs all products from a product section. It does not explicitly state when not to use the tool or contrast it with search and category siblings.

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