neon_execute_sql

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

No annotations are present, and the description omits critical behavioral details such as side effects, error handling, idempotency, or performance implications of executing SQL queries.

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?

While very concise, the description is too sparse to be valuable. Important information is missing, making brevity a detriment rather than a virtue.

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 6 parameters and no output schema, the description is critically incomplete. It fails to guide the agent on authentication, target specification, or result handling.

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?

Schema coverage is only 33%; the description adds no explanation for parameters like api_key, project_id, branch_id, or endpoint_id, leaving the agent to infer their meaning from names alone.

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 'Execute' and resource 'SQL query against a Neon database endpoint', clearly distinguishing it from sibling tools like 'neon_create_branch' or 'neon_list_projects' which manage infrastructure.

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 on when to use this tool, prerequisites, or alternatives. The single sentence provides no context for usage decisions.

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