export_csv

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

With no annotations, the description carries the burden of behavioral disclosure. It discloses the save location (file path or directory), the default filename (homebox-export.csv in the current directory), and the return value (path and row count). However, it does not specify overwrite behavior or how a directory value for save_to is handled (e.g., whether the default filename is used inside the directory), which leaves minor ambiguity.

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 primary purpose, and includes necessary details without redundancy. Every clause adds value: the complement/backup context, the parameter explanation, and the return value.

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 tool with one optional parameter and no output schema, the description is complete: it explains what is exported, how to specify the output location, what the default is, and what is returned. It also addresses the tool's relationship to import_csv. No critical missing information prevents an agent from invoking it correctly.

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 0%, so the description must compensate. It fully explains the only parameter, save_to: it is a file path or directory, with a default value of homebox-export.csv in the current directory. This adds crucial semantic meaning beyond the bare schema, making the parameter's behavior clear.

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 exports the whole inventory as a Homebox CSV (verb+resource+output). It distinguishes itself from siblings by explicitly noting it is the complement of import_csv, making its role unambiguous.

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 provides explicit context on when to use the tool: it is the complement of import_csv and serves as a quick backup. This gives clear usage guidance and implicitly excludes partial-export use cases, as it handles the whole inventory.

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