executeSupabaseSqlQuery

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions the read-only nature and that results are returned, but it does not clarify whether read-only is enforced, how errors are handled, or what the result format looks like. Given that this is an SQL execution tool, these details are important for safe and correct use.

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 that front-loads the core action and resource. Every word earns its place, with no unnecessary detail or repetition.

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 simple tool with one parameter and no output schema, the description provides enough context: the action, the resource (Supabase), and the read-only constraint. However, the absence of an output schema means the description could have elaborated on the result format, and there is no mention of execution limits or error behavior. Still, the core information is present and sufficient for basic use.

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 provides 100% coverage for the single 'query' parameter, but the description adds meaningful semantics by specifying that the SQL query must be read-only. This extra constraint helps the agent understand what kind of SQL is acceptable, going beyond the schema's generic 'The SQL query to execute.'

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's purpose: it executes a read-only SQL query against a Supabase database and returns results. The verb 'executes' and resource 'Supabase database' are specific, and the read-only qualifier helps distinguish it from sibling tools that target PostgreSQL or Neon.

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?

The description implies that this tool is used for read-only SQL queries on Supabase, but it does not explicitly contrast it with sibling tools like executePostgreSQLSqlQuery or executeNeonSqlQuery. There is no 'when to use' or 'when not to use' guidance beyond the tool's name and basic description.

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