connect_to_supabase_instance

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

Discloses that it fetches credentials from Alibaba Cloud and establishes a connection. No annotations are present, so the description carries the full burden. However, it does not detail behavioral traits like statefulness, idempotency, or side effects beyond connecting.

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?

Two sentences, front-loaded with purpose. No wasted words. Could be slightly more structured but remains concise and 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?

Covers the tool's purpose and parameter semantics via schema, but lacks return value info and details on state management (e.g., multiple connections, connection lifecycle). Given no output schema, this gap is notable.

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 covers all 3 parameters with descriptions (100% coverage). The description adds minimal extra meaning beyond the schema, e.g., 'by instance name' matches the schema. 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?

Clearly states 'Connect to a specific Supabase instance by instance name' with explicit action and resource. Distinguishes from siblings like 'disconnect_supabase_instance' and 'list_aliyun_supabase_instances'.

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 says 'After connecting, you can use all Supabase tools (list_tables, execute_sql, etc.)', providing clear context for when to use this tool. Lacks explicit 'when not to use' or alternatives, but the guidance is sufficient.

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