ChangeOrderList

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

There are no annotations, and the description only mentions deprecated status and a batch size limit. It does not disclose error handling, success/failure behavior, or side effects. For a mutation tool, this is insufficient.

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 sentence with a deprecation label, which is concise and front-loaded. However, it could be better structured with separate sections for deprecation and functionality.

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 no output schema, no annotations, and zero parameters, the description lacks details on operation types, response format, error conditions, or usage examples. The deprecation note is useful but insufficient for complete context.

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 input schema has zero parameters, so the baseline is 4 per the '0 params' rule. The description adds no parameter details, but the mention of 'batch of operations' implies a list parameter which is not reflected in the schema, creating a minor inconsistency.

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 tool is deprecated and that it sends a batch of operations to change order information (accept, ship, etc.). It specifies a max of 100 items per call. However, it does not distinguish itself from sibling tools like ChangeOrderListV2 or V3.

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. The deprecation implies it is not recommended, but no explicit alternative or context for usage is given.

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