⚠️ DESTRUCTIVE/SCHEMA: Import headered CSV into a table.

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

With no annotations, the description must disclose behavioral traits. It includes 'DESTRUCTIVE/SCHEMA' in the title and description, but does not specify what is destructive (e.g., overwriting data, affecting schema) or how errors are handled. The warning is vague and lacks detail about impact, rollback, or constraints.

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 identical to the title, offering no additional structure or information. While it is concise, it repeats the title and fails to front-load essential context. Conciseness is not valuable when the content is minimal and redundant.

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?

The tool is complex (12 parameters, destructive, no output schema), yet the description covers almost none of its behavior. It doesn't explain error handling, batching, encoding options, or the impact on the database schema. This is severely incomplete for a tool of this complexity.

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?

The description provides no information about any of the 12 parameters. Since schema description coverage is 0% and the input schema lacks per-property descriptions, the tool description should compensate, but it does not. Parameters like encoding, delimiter, batch_size, and coerce_types are entirely unexplained.

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 is provided on when to use this tool versus alternatives like bulk_insert or import_schema. There is no mention of prerequisites, such as whether the table must exist or if create_table is needed. The description simply states the action without contextualizing its use.

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