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

Annotations already declare this as a safe, read-only, idempotent operation. The description adds useful behavioral context by listing returned fields and noting that FLASH offers have a countdown deadline, though it does not discuss pagination or ordering behavior.

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 short and front-loaded: it first states what is listed, then summarizes return values, then highlights the FLASH distinction. Every sentence adds actionable information 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 low-complexity, two-parameter, read-only list tool with rich annotations and full schema coverage, the description covers scope, return fields, and the special FLASH behavior. No output schema is present, and the description adequately explains what comes back.

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%, so both the kind enum and limit are already well documented. The description adds only a small amount of meaning by mentioning FLASH countdown behavior, which is largely duplicative of 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?

The description gives a specific verb and resource: list active promotions and deals in a neighborhood directory, and it clarifies the returned offer fields. It is clear on its own, but it does not explicitly distinguish itself from nearby list_* siblings such as list_products or list_pricing_plans.

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?

Usage is implied by the scope 'active promotions and deals available in this neighborhood directory,' and the FLASH note suggests filtering context. However, there is no explicit when-to-use guidance, no when-not-to-use guidance, and no named alternatives.

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