cbs_save_dataset

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

Annotations indicate idempotentHint=true and destructiveHint=false, suggesting overwrite behavior. The description does not add details about file overwrite, error handling, or permission requirements. With annotations present, the bar is lower, but missing file behavior context limits transparency.

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 followed by a parameter list. While concise, the parameter list is redundant with the input schema. Still, it is front-loaded and not verbose, earning a 4.

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?

The tool saves to a file, but the description lacks details about file handling (overwrite behavior, required permissions, supported formats). An output schema exists, mitigating the need for return value details, but file behavior context is missing.

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%, so baseline is 3. The description repeats parameter meanings from the schema without adding new insights. It does not clarify parameter interactions beyond what the schema already provides (e.g., fetch_all vs top/skip).

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 'Saves a dataset to a CSV file,' specifying the verb and resource. It differentiates from siblings like cbs_save_dataset_to_duckdb (saves to DuckDB) and other query/list tools, making the purpose specific and 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?

No explicit guidance on when to use this tool versus alternatives (e.g., cbs_save_dataset_to_duckdb or cbs_query_dataset). The description only lists parameters without explaining context, prerequisites, or situations where this tool is preferred.

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