firestarter_bulk_list

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

Annotations already indicate write operation (readOnlyHint=false) and non-destructive (destructiveHint=false). The description adds critical behavioral context beyond these: batch size limit (100 per call), non-atomic partial failure semantics ('One bad item never blocks the others'), and response reporting exactly which succeeded/failed. This gives the agent realistic expectations about outcomes.

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?

A single dense paragraph that front-loads the core purpose and usage. It is efficient, but the phrase 'everything firestarter_list accepts per-item is accepted here too' is slightly verbose and could be tightened. Overall well-structured and scannable.

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-write tool with a complex schema and no output schema, the description is remarkably complete: it covers required fields, batch limits, partial failure behavior, and directs to the single-item alternative. An agent can call this correctly without additional 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% for the single `products` parameter. The description adds meaning beyond schema by highlighting which fields are required per item (product_name, base_price), that it accepts all fields from firestarter_list, and the 100-item limit. This enriches the schema without redundancy.

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?

States a specific verb (Create) and resource (MANY products at once), explicitly distinguishes from the single-product sibling firestarter_list and clarifies bulk migration use case. An agent understands exactly what the tool does and how it differs from alternatives.

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?

Provides explicit when-to-use (migrating existing catalog from CSV/spreadsheet) and when-not (for a SINGLE product, use firestarter_list instead, which has richer per-listing guidance). Also specifies batching for >100 products. This fully routes the agent to correct tool selection.

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