write_csv

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

With no annotations provided, the description carries the full burden for behavioral disclosure. It does disclose one side effect—creating the folder if missing—but omits other relevant behaviors such as whether an existing file is overwritten, whether the named matrix must already exist, and what happens on failure.

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 front-loaded sentence that states the core operation and a key side effect with no filler or redundant wording. It is appropriately concise for a simple two-parameter tool.

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?

Although an output schema exists, the description remains incomplete because it fails to explain the key `name` parameter and provides no usage context relative to sibling tools. The folder-creation detail is helpful, but it does not resolve the main operational ambiguities.

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 by explaining the parameters. It implies that `path` is the CSV file destination, but it never clarifies what `name` refers to—whether it is the matrix identifier, the output file name, or something else. This ambiguity is significant for an agent selecting and invoking the tool.

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 a specific action: writing a matrix to a CSV file. It also adds a concrete behavioral detail about creating missing folders. It does not explicitly differentiate from sibling `put_matrix`, but the CSV-file target makes the file-export purpose reasonably distinct.

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 no guidance on when to use this tool versus alternatives like `read_csv`, `put_matrix`, or `get_matrix`. The intended use is only implied by the phrase 'Write a matrix to a CSV file', with no stated exclusions or comparison to sibling tools.

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