brc_batch_products

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

Describes the confirmation pattern and max items per request, but lacks details on what happens during the batch (e.g., validation, error handling, idempotency). No annotations provided, so description carries the full burden but is incomplete.

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?

Three sentences, no redundancy, front-loaded with key info. Every sentence adds essential context about the confirmWrite workflow and limits.

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?

Covers the core workflow but lacks details on return value structure (no output schema), the flexible items schema (what fields are expected), and error conditions. For a batch tool with complex behavior, more completeness is needed.

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%. Description adds context for priceBasis (enum explanation), confirmWrite (workflow), confirmCrAnalysisCategory (when to use), and companyName (example). Adds meaningful value beyond the schema's descriptions.

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 states 'Processes a batch of products' which is a verb+resource, but doesn't specify whether it creates, updates, or deletes. The workflow details suggest it's likely creating or updating, but the core action is vague. Distinguishes from siblings by referring to batch processing of products specifically.

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?

Explicitly describes the two-step workflow with confirmWrite, including when to set it to true and that preflight is not confirmation. However, does not compare to other batch tools or single-entity create/update tools, so integration with alternatives is implied.

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