delimit_data_migrate

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

No annotations provided, so description carries full burden. States 'Side effects: read-only inspection.' and 'Calls backends.tools_data.data_migrate.' Clearly indicates no destructive actions. Lacks details on permissions, error handling, or output format, but output schema may cover that.

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?

Concise and well-organized: one-sentence purpose, then bullet-like sections for usage, contrast, and side effects. No unnecessary words, every sentence adds value.

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?

Covers purpose, usage guidelines, side effects, and parameter meaning. With an output schema, return values do not need to be described. Slightly lacking in detailing what the inspection output looks like, but overall sufficient for a simple read-only 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?

Input schema has 100% coverage for the single parameter 'target', with description 'Project path to scan for migration files. Default "." (cwd).' The description does not add additional semantic value beyond the schema, so baseline 3 is appropriate.

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?

Starts with 'Inspect migration files (alembic / Django / Prisma / Knex) for status.' Clearly states verb (inspect) and resource (migration files) with specific types. Distinguishes from siblings by contrasting with delimit_data_validate and delimit_data_backup.

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?

Explicitly provides when to use ('audit pending and applied migrations before a deploy, or as a CI gate'), when not to use ('to actually apply migrations' or 'back up data first'), and mentions alternative tool (delimit_data_backup). Includes sibling contrast.

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