executeNeonSqlQuery

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

With no annotations provided, the description carries the full burden. It explicitly states 'read-only', which is a key behavioral trait and sufficient for the agent to understand there are no write side effects. However, it does not disclose other behaviors like query result formatting, limits, or error handling, so it is not exhaustive but still valuable.

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 one clear, front-loaded sentence of about 15 words. Every word is purposeful, stating the action, the read-only scope, the target database, and the output. There is no redundancy or fluff.

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?

The tool has low complexity (1 param, simple read-only query), and the description provides the essential purpose. However, there is no output schema, and the description does not detail the result format or specify when to use this vs. sibling SQL executors. It is adequate but has clear gaps in guidance and result semantics.

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 input schema has 100% coverage: the single 'query' parameter is described as 'The SQL query to execute.' The tool description adds no additional meaning or syntax details beyond this, so the baseline of 3 applies.

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 uses a specific verb ('Executes') and identifies the target resource ('Neon database') with a clear scope ('read-only SQL query'). It distinguishes itself from sibling tools like executePostgreSQLSqlQuery and fetchNeonSchema by naming the database type 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?

The description implies the tool is for read-only SQL queries against Neon, but it does not explicitly state when to use it over alternatives (e.g., executePostgreSQLSqlQuery for other Postgres databases, fetchNeonSchema for schema discovery) or provide any exclusions. Usage context is implied but not explicitly guided.

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