beel_create_products_bulk

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

Beyond the annotations (which only mark it as a non-read-only, non-destructive write operation), the description discloses the important partial-processing behavior: each product is handled independently, and rejected rows are reported while others are created. This adds significant context about failure handling and what to expect, which is valuable for an agent invoking the 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?

The description is two sentences, front-loaded with the core action (create up to 100 products) and immediately followed by the key behavioral nuance (partial processing). It is efficient, contains no fluff, and includes the endpoint as a helpful reference. Every sentence earns its place.

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 bulk creation with nested tax rules and many possible validations, the description covers the main operation and the partial failure mode but does not explain the structure of the report or how rejected rows are communicated, nor does it mention idempotency semantics (though these are in the schema). Since no output schema is provided, the description could have elaborated on the response, but the rich schema mitigates this gap. A 3 reflects that it is adequate but not fully complete.

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 does not add parameter-level meaning beyond the schema; it only mentions 'NIF' which is already described in the company_id parameter. With schema description coverage at 67%, the schema already documents most parameters (including nested objects like TaxInfo with detailed rules), so the description does not need to repeat them. A baseline 3 is appropriate.

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 action: 'Creates up to 100 products in the catalog of this company (NIF)' and provides the endpoint. It distinguishes this bulk creation from the single create by specifying the capacity and the partial-processing behavior, which is a unique trait. It is not a tautology and gives a concrete resource and scope.

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 its usage for bulk product creation with a clear limit (up to 100) and explains the partial processing, which indicates when it would be appropriate (many products at once). However, it does not explicitly name alternatives like the single-product creation tool or state when not to use it, so it lacks explicit exclusions.

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