executeQuery

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

No annotations provided, so description covers key behaviors: supported statements, DDL exclusion, row limit for SELECT/EXPLAIN, and context usage. Could be more explicit about side effects of write operations, but overall transparent.

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?

Four well-structured sentences, each adding value. Purpose stated first. No redundant or unnecessary 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?

Covers return behavior (up to 200 rows for SELECT/EXPLAIN), parameter context, and sibling tools. Lacks explicit statement that INSERT/UPDATE/DELETE return no rows, but implied. Good overall.

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 100% with clear descriptions for each parameter. Description adds context about 'current context' for connectionId and schema, which is not in schema 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?

Description clearly states the verb 'execute', resource 'SQL query on database', and specific supported statement types (SELECT, INSERT, UPDATE, DELETE, EXPLAIN). It explicitly distinguishes from sibling tools by disallowing DDL and referencing createTables/modifyTables.

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?

Provides explicit guidance on when to use (for DML and SELECT/EXPLAIN) and when not (DDL). Names alternatives (createTables, modifyTables) and explains context usage.

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