executeSupabaseSqlQuery

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

No annotations are present, so the description carries the transparency burden. It discloses the critical read-only behavior, preventing accidental mutations, and states that results are returned. It does not mention permissions, limits, or error behavior, but for a simple query tool the core safety trait is covered.

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?

Single sentence, front-loaded with the action, no redundant words. Every word ('read-only', 'Supabase', 'returns results') adds value.

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?

For a one-parameter read-only query tool, the description provides adequate context: target database, read-only behavior, and return value. It doesn't detail output structure, but no output schema is provided and the behavior is straightforward. It could have mentioned differences from other SQL execution tools, but the core completeness is sufficient.

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 schema describes the query parameter simply as 'The SQL query to execute.' The description adds essential restriction that it must be a read-only SQL query and that it targets Supabase, giving the parameter meaningful constraints beyond the schema. With 100% schema coverage, baseline is 3; the added read-only semantics justify a 4.

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 tool executes a read-only SQL query against Supabase and returns results. It distinguishes from sibling tools like fetchSupabaseSchema (schema retrieval) and executePostgreSQLSqlQuery (different database) by specifying the target database and read-only nature.

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?

Provides clear context that this is for read-only queries on Supabase, implying it should not be used for write operations or for other database types. However, it does not explicitly name alternatives like executeNeonSqlQuery or executePostgreSQLSqlQuery, so it lacks the strongest guidance.

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