keepa_add_promo

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

With no annotations provided, the description carries the full burden of disclosing behavior. 'Register' implies mutation but does not explain side effects, reversibility, permissions, return values, or error conditions. The description only gives examples of promo types, not operational specifics.

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 a single, front-loaded sentence with exactly one verb and resource. It is efficient, concise, and free of filler words.

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?

Given 6 parameters, 3 required, no output schema, and no annotations, the description is too minimal. It does not explain the return behavior, validation rules, idempotency, or how this tool fits into the promo workflow (e.g., relation to keepa_list_promos or keepa_analyze_promo_impact).

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 the schema already documents all parameters. The description's examples of promo types (coupon, deal, Lightning Deal) are redundant with the schema's own examples. The description adds no meaningful new parameter semantics.

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 'Register' and resource 'promotional event for an ASIN', with examples like coupon, Lightning Deal. This clearly distinguishes it from sibling tools such as keepa_list_promos (listing) and keepa_analyze_promo_impact (analysis).

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?

The description provides no guidance on when to use this tool versus alternatives, no prerequisites, exclusions, or mention of related tools. It is a bare statement of action without contextual usage instructions.

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