firestarter_bulk_list

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

The description adds significant behavioral context beyond annotations: it discloses partial-failure behavior ('One bad item never blocks the others'), defines the batch size limit, and specifies per-item required fields. While annotations already indicate this is a write (readOnlyHint:false), the description enriches understanding of error handling and constraints without contradicting any annotation.

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 concise and well-structured: it leads with the core purpose, then provides batch limits, failure semantics, and an explicit alternative. Every sentence delivers actionable information without redundancy or filler, making the description highly scannable and efficient.

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 bulk-create mutation tool with one complex parameter and no output schema, the description provides all essential context: what it does, when to use it, the 100-item cap, partial failure handling, and the single-item alternative. It fully compensates for the lack of an output schema by describing the response's key behavior (success/failure per item).

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 description coverage is 100%, so the schema fully documents all parameters. The description reinforces the required fields (product_name, base_price) and notes that 'everything firestarter_list accepts per-item is accepted here too', which adds a helpful cross-reference, but it does not deeply elaborate on parameter syntax or formats beyond what the schema already states.

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 opens with a specific verb+resource+scope: 'Create MANY products at once', immediately conveying the tool's batch-listing purpose. It clearly distinguishes from firestarter_list by stating 'For a SINGLE product, use firestarter_list instead', making the differentiation explicit.

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 gives concrete usage context: 'for migrating an existing catalog (e.g. from a CSV or spreadsheet)', and provides explicit guidance on batch limits ('Up to 100 products per call — for more, call this tool again'), required fields, and the single-product alternative. This fully equips an agent to decide when to use this tool.

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