Create discounts

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

Beyond annotations (readOnly=false, etc.), the description discloses critical behaviors: 100-item limit, undocumented key names inside nested maps, no list/delete endpoint, and verbatim passthrough of undocumented response body. This adds substantial value.

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?

Three sentences: purpose, key constraint, and essential warnings. Every sentence earns its place with no fluff. Front-loaded with the primary action.

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?

Despite no output schema, the description explains the undefined response (2xx = success, returned verbatim) and covers limitations (key names, no list/delete). This is complete for a create tool with known upstream gaps.

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 covers 100% of parameters and describes them as string→string maps. The description adds the crucial warning about undocumented key names and 'passed through verbatim', reinforcing and extending schema meaning beyond 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?

The description clearly states the verb 'Creates' and the resource 'per-store product discounts', includes the endpoint path (POST /b2b/v1/discounts/create), and distinguishes it from siblings like create_products and create_order by specifying per-store product discounts.

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 implies use for creating discounts but does not explicitly discuss when to choose this over alternatives or when to avoid it. The caveat about undocumented key names is caution, not tool-selection guidance.

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