Delimit Data Migrate

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

Annotations already mark this as read-only and non-destructive, and the description reinforces this with 'read-only inspection' and 'this tool only inspects status.' It adds useful behavioral context that the tool does not apply migrations and names the backend call, going slightly beyond the annotations.

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 organized into clear, front-loaded sections: purpose, when to use, when not to use, sibling contrast, and side effects. Every sentence earns its place; the backend call detail is minor but does not bloat the description.

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?

For a simple read-only tool with one optional parameter, an output schema, and strong annotations, the description is complete. It covers use cases, exclusions, safety profile, and scope without needing to explain return values since an output schema exists.

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 100%, so the single optional 'target' parameter is fully documented in the input schema. The description adds no additional parameter-level detail, but none is needed given the schema already explains the default and purpose.

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: 'Inspect migration files (alembic / Django / Prisma / Knex) for status.' It clearly distinguishes itself from siblings by naming delimit_data_validate and delimit_data_backup and stating what this tool does not do.

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 explicitly states when to use the tool ('to audit pending and applied migrations before a deploy, or as a CI gate') and when not to use it ('to actually apply migrations... or back up data first'). It also provides sibling contrast, leaving no ambiguity about which tool to select.

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