batch_products

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

No annotations are provided, so the description carries the full burden. It discloses batch size and upsert behavior but does not mention potential side effects (e.g., permanent deletion), authentication requirements, or rate limits. For a mutation tool, this is adequate but lacks depth.

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 extremely concise: three sentences that front-load the core purpose and constraints. Every sentence adds value, with no redundancy or filler.

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 complexity of a batch mutation tool and the absence of an output schema or annotations, the description covers the essential information: what it does, batch limits, and upsert behavior. Minor gaps include lack of return format details and error handling, but it is sufficient for correct tool selection.

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 already describes all three parameters with 100% coverage. The description adds only the batch size constraint (up to 5,000) and clarifies upsert support, which reinforces schema descriptions. It does not significantly augment parameter meaning.

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 performs batch create, update, or delete operations on products in a catalog, which is distinct from the individual create/update/delete tools in the sibling list. It also specifies limits (up to 5,000 items) and the upsert capability, leaving no ambiguity about the tool's purpose.

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 this tool is for batch operations while individual product tools exist for single-item actions. It does not explicitly say when not to use it or provide alternatives, but the context (e.g., limit of 5,000) gives clear guidance for appropriate usage.

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