run_migrate

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

With no annotations, the description must disclose behavioral traits. It only states 'apply pending migrations' and the delegated command, but does not clarify that this modifies the database schema, whether it is reversible, what 'pending' means, or what permissions are required. The agent has little insight into side effects or safety.

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 very short (two sentences) and to the point. It contains no filler or redundant information. However, it could be slightly more structured (e.g., a sentence about what happens after execution) without losing conciseness.

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 lack of output schema, annotations, and parameters, the description is too sparse. It does not explain the outcome (e.g., success indications, error cases), the scope ('local D1' is mentioned but not elaborated), or how it relates to the migration lifecycle. An agent may not know what to expect after calling this 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?

The tool has zero parameters, so the input schema fully covers the interface. Baseline for 0 parameters is 4. The description does not need to add parameter semantics, as there are none.

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 clearly states the tool applies pending migrations, a specific verb+resource combination. It adds context by mentioning delegation to a specific command ('d1-eloquent migrate') and target ('local D1'). However, it does not explicitly distinguish from sibling tools like 'run_fresh' or 'run_rollback', which are also migration-related.

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 such as 'run_fresh', 'run_rollback', or 'migration_status'. The description lacks any context about prerequisites, typical workflow, or scenarios where this tool is appropriate.

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