update_code_discount_free_shipping

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

No annotations provided. The description indicates it's a mutation ('update') with partial updates, but lacks details on permissions, reversibility, or side effects. Minimal transparency for a 14-parameter tool.

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?

One concise sentence (10 words) that efficiently states the tool's purpose and partial update behavior. No unnecessary 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 14 parameters, no output schema, and no annotations, the description is insufficient. It doesn't explain return values, prerequisites, or side effects. Completeness is lacking for a complex update tool.

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-level information beyond the schema. With only 14% schema description coverage, the burden falls on the description to clarify parameter meaning, but it only states 'only provided fields are changed,' which is behavioral, not semantic.

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 'Update an existing free shipping code discount' with a specific verb and resource. It differentiates from creation tools, but does not explicitly distinguish from other update discount tools like update_code_discount_basic.

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 on when to use this tool versus alternatives like update_code_discount_basic or update_automatic_discount_free_shipping. The only hint is the partial update behavior, which is implied rather than explicit.

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