bulk_create_product_reviews

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

With no annotations, the description carries full burden. It lists side effects: adds multiple comments, potential immediate/reviewed publication, affects average rating, and partial failure behavior. Missing authentication or rate limit details, but still strong.

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 well-structured with sections for write operation, purpose, API call, return structure, and side effects. Every sentence is valuable and front-loaded with the main action.

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?

For a 1-parameter bulk create tool with no output schema, the description provides comprehensive details: use case, API endpoint, return format, and side effects. It adequately covers all necessary 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?

Schema coverage is 100% with a clear description of the 'reviews' parameter. The description repeats the schema's explanation but does not add additional semantics beyond the example format.

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 verb '批次建立' (batch create) and resource '商品評論' (product reviews), with explicit use cases for bulk importing historical reviews or post-promotion entries. It distinguishes itself from single create and other bulk tools.

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 explicit context for when to use (bulk imports, post-promotion) but does not include when-not-to-use or direct comparisons to alternative tools like 'create_product_review' or 'bulk_update_product_reviews'.

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