⚠️ FILE WRITE: Export a table or read-only SELECT/PRAGMA/EXPLAIN query to a CSV file. Can write absolute paths. Provide exactly one of table or query.

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

No annotations are provided, so the description must cover behavior. It warns about file write and absolute paths, and restricts queries to read-only types. But it lacks detail on overwrite behavior, side effects of append, default encoding, or required permissions. The warning icon is present but not elaborated.

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, efficient sentence that front-loads the important warning symbol and key constraint. While brief, it avoids verbosity. However, the conciseness sacrifices necessary detail for parameter semantics and usage context.

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 the high parameter count (9) and absence of output schema, the description is insufficiently complete. It does not explain return values, error conditions, or how default values work. The minimal coverage leaves significant gaps for the agent to interpret 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?

With 0% schema description coverage, the description must clarify parameters. It only explains that 'table' and 'query' are mutually exclusive. The remaining seven parameters (file_path, append, encoding, delimiter, always_quote, database_name, record_delimiter) are not mentioned, leaving the agent uninformed about their purpose and constraints.

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?

Tautological: description restates name/title.

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?

It instructs to provide exactly one of 'table' or 'query' and warns about absolute file paths. However, it omits guidance on when to choose this tool over export_json, export_xlsx, or import_csv, and does not mention the append or encoding options.

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