supabase_migration_new

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

No annotations are present, and the description only states a basic action ('Create'). It fails to disclose side effects such as file creation on disk, potential overwrite behavior, or dependencies on the Supabase CLI. For a writing operation, this is insufficient.

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 and thus concise, but it is overly minimal. It omits useful information that would justify its length, earning an average score for being neither verbose nor informative.

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 simplicity (1 parameter, no output schema, no annotations), the description should still provide context like expected output (e.g., file path) or CLI requirements. It fails to complete the picture, leaving the agent underinformed.

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 input schema provides a 'name' parameter with description 'Migration name', achieving 100% coverage. The tool description adds no additional meaning beyond the schema, so the baseline score of 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?

The description clearly states the verb 'Create' and the resource 'new migration file', distinguishing it from sibling tools like create_migration_with_rollback. However, it does not specify the context (e.g., using Supabase CLI) or the file's location, which slightly reduces clarity.

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 create_migration_with_rollback. The description lacks any context about prerequisites or typical use cases, leaving the agent without decision support.

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