⚠️ FILE WRITE: Export a table or read-only SELECT/PRAGMA/EXPLAIN query to an XLSX file (one sheet, first row = headers). 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 carries full burden. It mentions file write capability and absolute paths (security concern) but lacks details on permissions, overwrite behavior, return value, or error conditions. Adequate but not thorough.

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 concise and front-loaded with a warning. However, it repeats the title verbatim, making it redundant. Every sentence is meaningful but could be more efficient.

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 complexity (5 parameters, 1 required) and lack of annotations or output schema, the description is insufficient. It omits details on return format, error handling, and interactions with sibling tools like import_xlsx.

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 0%, yet the description does not describe individual parameters. It only mentions table/query exclusivity and file_path being absolute. No info on sheet_name, database_name, or their constraints (max length, default). Minimal added value.

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?

The description gives explicit usage guidance: provide exactly one of table or query, and only read-only queries are allowed. It implies when to use this tool (for XLSX output) but does not contrast with alternatives like export_csv or export_json.

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