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

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

Discloses file write capability and absolute path usage, and restricts queries to read-only types. However, does not mention default behavior for overwriting (append parameter exists but not described), leaving a gap in behavioral 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?

Single sentence with a warning emoji is concise and packs essential info. Could be slightly better structured with separate lines for constraints, but overall no wasted words.

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?

Despite mentioning table/query and file write, the description omits critical details: append behavior, encoding options, database_name context, and the exact file_path format. This is insufficient for a 6-param write tool with no output schema.

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 only adds meaning for table and query parameters. File_path is implied but not described in format or constraints. Append, encoding, and database_name are entirely unmentioned.

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?

Provides one key guideline: 'Provide exactly one of table or query.' However, no guidance on when to use this tool versus alternatives like export_csv or export_xlsx, nor when not to use it.

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