update_code_discount_basic

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

The description states 'Only provided fields are changed,' which discloses partial update (PATCH) behavior. However, no annotations are present, and the description does not cover permissions, idempotency, side effects, or whether certain parameters require simultaneous updates. The partial update note is useful but minimal.

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 very short (two sentences) and front-loaded with the core purpose. It is concise but could be more informative without sacrificing brevity. The partial update behavior is stated in the second sentence, which is appropriate.

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 the tool has 17 parameters and no output schema, the description is insufficient. It lacks details on return values, error handling, required permissions, or the effect of omitting fields. The description only covers the basic operation and partial update aspect.

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 description adds no parameter-specific information beyond what the input schema provides. With only 18% schema description coverage, the description should compensate but does not mention any parameter details, formats, or constraints.

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 it updates an existing basic (amount-off) code discount. The verb 'update' and resource 'basic code discount' are specific. The parenthetical '(amount-off)' helps distinguish from other discount types, though it does not explicitly differentiate from sibling tools like update_code_discount_bxgy.

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?

No guidance is provided on when to use this tool versus alternatives such as update_code_discount_bxgy or update_code_discount_free_shipping. There are no prerequisites, exclusions, or context about when not to use this tool.

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