supabase_db_reset

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

Without annotations, the description should disclose that resetting is destructive and irreversible. 'Reset local database to initial state' implies data loss, but does not explicitly state the behavioral traits.

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?

Extremely concise (5 words), no filler. Appropriate for a simple tool with no parameters.

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?

The tool has no parameters and no output schema, so the description should clarify what 'initial state' means (e.g., schema only, seed data, or empty). It also lacks safety warnings for a destructive operation.

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?

With zero parameters, baseline is 4. No additional info is needed beyond the schema, which fully covers the parameter space.

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 action (reset) and resource (local database) and outcome (to initial state). It provides a specific verb and resource, but does not differentiate from siblings like rollback or deploy migration.

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 on when to use this tool vs. alternatives like 'rollback_last_migrations' or 'supabase_db_push'. The description omits that it is destructive and intended for local development only.

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