execute_query

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

No annotations provided, so description bears full burden. It discloses read-only nature and allowed SQL statement types (SELECT, SHOW, etc.), but does not describe return format, error behavior, or any other side effects. Lacks details beyond the schema.

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 brief (one English sentence plus Korean translations). The Korean is extraneous for an English-context AI, making it slightly less concise. However, the core message is front-loaded and no unnecessary elaboration exists beyond the translation.

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?

Given two parameters, no output schema, and sibling tools, the description is adequate but incomplete. It fails to explain the result format or behavior, leaving the agent to infer from the SQL nature. The schema covers statement restrictions, but overall completeness is average for a simple tool.

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 both parameters well-described in the schema. The description adds minimal additional meaning beyond stating 'read-only' and providing Korean translations, which do not enhance semantic understanding for an English-speaking AI.

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 it executes a read-only SQL query, with specific verb 'Execute' and resource 'SQL query'. The read-only constraint and the list of allowed statements in the schema help distinguish it from siblings like analyze_query or explain_query.

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 explicit guidance on when to use this tool vs. alternatives. The description does not mention when not to use it or suggest sibling tools. Usage is implied by the name and schema but not clearly articulated.

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