base_readQuery

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

Despite having no annotations, the description does not disclose the behavioral traits beyond the basic execution flow. It fails to mention whether the query is read-only or can modify data, whether it commits transactions, or how errors are handled. The description mentions persisting results but does not clarify side effects like table creation permissions or cleanup.

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 concise, with a front-loaded main sentence that captures the core functionality, followed by a clear list of arguments and return type. Every sentence adds value without redundancy, and the structure is easy to scan.

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 SQL execution tool with no output schema, the description is incomplete. It does not describe the structure of the returned results (e.g., rows, columns, data types) or how errors are reported. It mentions 'volatile_table' in metadata but omits the main result format. Additionally, it does not specify whether the tool supports DDL, DML, or only SELECT, which is critical for safe usage.

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 description adds significant meaning beyond the schema: it explains that 'sql' can contain bind-parameter placeholders and 'persist' creates a reusable table. Since schema description coverage is 0%, these explanations are crucial. However, it could be improved by detailing the format of bind parameters (e.g., named or positional) and the lifetime or namespace of persisted tables.

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 that the tool executes a SQL query, binds parameters, and returns rendered SQL in metadata. It distinguishes itself from sibling tools by specifying the use of SQLAlchemy and the return of fully rendered SQL. However, it does not explicitly state the scope of allowed SQL statements (e.g., SELECT only) or how it differs from other query tools like sql_Execute_Full_Pipeline.

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 is provided on when to use this tool versus its siblings (e.g., when to use base_readQuery instead of sql_Analyze_Cluster_Stats or sql_Execute_Full_Pipeline). The description does not mention any prerequisites, constraints, or recommendations for usage, leaving the agent without contextual decision-making information.

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