deploy_supabase_to_coolify

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

No annotations provided, so description carries full burden. Only states 'Deploy' without disclosing side effects (e.g., overwriting existing instances, required permissions). No mention of destructive or non-destructive nature.

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 concise sentence, front-loading the core purpose. It earns its place by stating the action and target, though it could add more value without losing conciseness.

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?

No output schema, and description omits crucial details like what the config object expects, prerequisites (e.g., Coolify setup, Supabase CLI), and post-deployment behavior. Incomplete given tool complexity and number of sibling tools.

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 baseline is 3. Description adds context that the tool deploys a 'complete Supabase instance', which implies config should contain Supabase-specific settings, but does not elaborate on config structure beyond schema.

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?

Description states 'Deploy a complete Supabase instance on Coolify', providing a clear verb and resource. It distinguishes from sibling tools like deploy_coolify_application (generic app) and deploy_edge_function, but could be more specific about what a 'complete Supabase instance' entails.

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 versus sibling deployment tools (e.g., deploy_coolify_application, deploy_migration). Does not mention prerequisites or alternatives.

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