update_automatic_discount_basic

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

No annotations provided. Description discloses partial update behavior but lacks other behavioral traits such as prerequisites (discount must exist), idempotency, side effects, or error handling. Bar is higher due to no annotations.

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?

Two sentences, concise and front-loaded: first sentence states verb and object, second adds important nuance. No wasted 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?

Despite complexity (14 params, nested objects, no output schema), description is very brief. Missing details on behavior when discount not found, idempotency, return value, or required fields beyond 'id'.

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 only 14% (only 'id' described). Description adds no parameter explanations beyond 'Only provided fields are changed', failing to compensate for low coverage. Does not explain semantics of any parameter.

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?

Description clearly states 'Update an existing basic automatic discount', specifying verb (update) and resource (basic automatic discount). Differentiates from siblings like create_automatic_discount_basic and other update discount types (bxgy, free_shipping).

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?

Description implies usage context (updating existing discount with partial update via 'Only provided fields are changed') but provides no explicit guidance on when to use this vs other update discount tools or when not to use it.

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