execute_sql

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 and does so comprehensively. It specifies critical security behaviors (never display credentials, use read-only queries), operational constraints (proper query sanitization), and detailed return format (query results with column names, typed values, row count, metadata, execution status). This provides rich behavioral context beyond basic functionality.

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 well-structured with clear sections (purpose, returns, warnings, args, returns) and front-loads key information. However, the 'Returns' section appears twice with slightly different wording, creating minor redundancy. Most sentences earn their place by providing essential information.

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 complex SQL execution tool with 7 parameters, no annotations, and no output schema, the description does an excellent job covering security constraints, return format, and parameter semantics. The main gap is incomplete parameter documentation (missing username/password/ctx explanations), but otherwise it provides substantial context for safe and effective tool 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?

With 0% schema description coverage for 7 parameters, the description compensates by providing semantic explanations for 4 parameters (workspace_group_identifier, workspace_identifier, database, sql_query) in the Args section. However, it doesn't explain the username and password parameters mentioned in the schema, leaving some parameter meaning undocumented. The ctx parameter is also unexplained, though it appears to be optional with a default null value.

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 verb ('execute SQL operations') and resource ('on a database attached to workspace within a workspace group'), making the purpose specific and unambiguous. It distinguishes this from sibling tools like 'execute_sql_on_virtual_workspace' by specifying it works on databases attached to workspaces within workspace groups, not virtual workspaces.

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 provides explicit guidance on when to use this tool versus alternatives through the security warnings section, which specifies 'Use only READ-ONLY queries (SELECT, SHOW, DESCRIBE)' and lists prohibited operations. This clearly defines the appropriate use case and distinguishes it from tools that might allow modifications.

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