import_csv

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

With no annotations provided, the description carries full weight and delivers: it discloses auto-creation of location hierarchies, the requirement that tags already exist, location-only row behavior, the need to call finalize_photos after upload, and the return value. This is robust behavioral disclosure for an import 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 longer than average but every sentence carries essential information. It is front-loaded with a clear purpose, then structured into pipeline context, column list, special cases, and follow-up instructions. The density is justified by the tool's complexity, though it could be slightly tighter.

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 one parameter, no output schema, and high complexity (many columns, auto-creation behavior), the description addresses all key aspects: input format, required preconditions (tags), side effects (location creation), post-import steps, and return type. It leaves little ambiguous for an agent.

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 schema provides only a single parameter (csv_text) with zero description coverage. The description completely compensates by enumerating all recognized columns (HB.name, HB.location, etc.), explaining location path semantics, and specifying constraints like tag existence. It turns an opaque text blob into a well-defined input format.

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: 'Bulk-create items and locations from a Homebox CSV'. This clearly distinguishes it from sibling tools like create_item and create_location, and the 'bulk creator' phrasing reinforces its unique role in the photo-intake pipeline.

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 identifies the tool as the 'bulk creator for the photo-intake pipeline' and notes it 'avoids ~4 API calls per item', implying use for multi-item imports. It also references associated tools (list_tags for tag validation, finalize_photos after import) but does not explicitly state when to use single-item alternatives like create_item.

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