import_accessories_csv

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

No annotations are provided, and the description does not disclose behavioral traits such as whether existing records are overwritten, error handling, atomicity, or authentication requirements. Only file size and header format are mentioned.

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 a single sentence with essential details (file size, required headers) front-loaded. No redundancy or unnecessary words.

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 no output schema, the description lacks information on what the tool returns after import (e.g., success count, errors). It also does not cover duplicate handling or validation behavior, making it insufficient for a bulk import operation.

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 single parameter 'file' has 100% schema description coverage already explaining it is a local CSV path. The tool description adds no further semantic value beyond the schema, so baseline score applies.

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 tool imports multiple accessories from a local CSV file, specifies file size limit (10MB), and lists required headers. It is distinct from siblings like import_componen_products_csv or create_accessory.

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 bulk import use case but does not explicitly state when to use this tool over alternatives like create_accessory for single item or list_accessories for viewing. No exclusion criteria or scenario guidance provided.

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