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

The description discloses non-obvious output behavior: CSV produces one file per table and zips when there are several, JSON keys objects by table, and Excel always creates a single workbook with one worksheet per table. This goes well beyond the annotations, which only indicate readOnlyHint=false and destructiveHint=false.

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 front-loaded with the core purpose, then expands into output-format specifics and the optional parameter in a compact, well-organized way. Every sentence earns its place, with only a minor category tag as light supplemental noise.

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?

There is no output schema, so the description appropriately explains what the caller should expect from each target format, including multi-table behaviors. It is complete enough for the tool's moderate complexity, though it does not mention delivery mechanics or error conditions.

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 100%, so the input schema already documents all three parameters well. The description adds some reinforcement, such as explaining that passing 'table' exports a single table, but it does not significantly extend the schema's parameter semantics.

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 opens with a specific verb and resource: 'Export a SQLite database (.db/.sqlite) to CSV, JSON or Excel.' This clearly identifies the tool's function and scope, and the format list differentiates it from generic sibling tools like convert_file or convert_data.

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 clear context for when to use the tool — whenever a SQLite database needs converting to CSV, JSON, or Excel. It also explains usage trade-offs like CSV being zipped with multiple tables and when to pass the optional 'table' parameter, though it does not explicitly compare against alternative conversion tools.

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