⚠️ FILE WRITE: Export table or read-only query to CSV.

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

With no annotations provided, the description must disclose behavioral traits. It includes a 'FILE WRITE' warning but does not explain behaviors like overwriting, appending, file handling, permissions, or side effects. The label is superficial and lacks substantive disclosure.

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, which is concise in length, but it is under-specified. It does not earn its place as it omits critical information; brevity here is a symptom of incompleteness rather than effective structure.

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 9 parameters, no annotations, no output schema, and no parameter documentation, the description is grossly incomplete. It does not address return values, file write semantics, or any usage context. The tool needs substantial additional detail to be safely and correctly invoked.

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% (context signal). The description does not explain any of the 9 parameters, including required file_path, optional query/table, append, delimiter, encoding, etc. It adds no meaning beyond the schema, which is unacceptable given the parameter count.

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?

No guidance on when to use this tool versus alternatives such as execute_read_query for querying data or export_schema for schema exports. The description implies usage for CSV file creation but does not provide context, exclusions, or alternatives.

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