database_import

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

Explicitly warns 'DESTRUCTIVE: the SQL runs as-is, so a dump containing DROP/CREATE will replace existing tables and data.' Describes auth and path restrictions. With no annotations, this carries full burden and does well.

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?

Description is moderately sized but each sentence adds essential info. Front-loaded with main action. Could be slightly tighter but no unnecessary 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?

Given no annotations or output schema, description covers: action, inputs, environmental constraints (SSH, staging dir), safety mechanism (dry_run/confirm). Complete for a database import tool.

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 50% for required parameters. Description adds context for source_path (staging dir requirement) and boolean params (dry_run preview, confirm execute). Adds value beyond schema.

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?

Description clearly states action: 'Load a .sql dump file INTO a database via SSH (mysql)'. It distinguishes from sibling tool database_dump by mentioning it as an alternative to produce the file. The verb 'Load' and resource 'database' are specific.

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 usage context: file must be in staging dir, targets local MySQL via root socket, requires SSH configured. Mentions dry_run and confirm parameters for safe execution. Could explicitly state when not to use but adequately covers when and how.

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