supabase_migration_list

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

No annotations are present, so the description carries the full burden. It only says 'List all migrations (CLI)', which implies a read-only operation but does not explicitly state that it is non-destructive or disclose any behavioral traits such as network calls or data source.

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 (3 words), which is concise, but it sacrifices necessary detail. It could include a sentence about the output or context without becoming verbose. The dimension rewards front-loading, but here it is too sparse.

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?

With no output schema, no annotations, and a minimal description, the tool is incomplete. It does not explain what 'migrations' refers to, what the list contains, or how it differs from the sibling 'list_migrations' tool. The agent has insufficient information to decide when to invoke it.

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 has zero parameters, so there is no need to describe parameters. The description adds no parameter information, but that is acceptable given the schema. Baseline score of 4 for 0-parameter tools.

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 states 'List all migrations (CLI)', which indicates the verb and resource, but it does not differentiate from the sibling tool 'list_migrations' that likely serves a similar purpose. The addition of '(CLI)' hints at context but is insufficient for clear differentiation.

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 like 'list_migrations' or other migration-related tools. There is no mention of prerequisites, context, or exclusions.

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