execute_sql

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

With no annotations, the description is the sole source of behavioral disclosure. It only states that it executes a query and returns results, but does not mention potential side effects, permissions required, rate limits, or whether the query can modify data. This leaves the agent in the dark about risks associated with arbitrary SQL execution.

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 a single, clear sentence that conveys the core purpose without any redundant words. It is front-loaded and efficiently structured, every word earning its place.

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?

Although an output schema exists and the tool has only two parameters, the description is incomplete for practical use. It lacks usage guidelines, parameter clarification, and behavioral nuance (e.g., whether the query is read/write). This is insufficient for an agent to select and invoke the tool reliably.

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 provides only parameter names (service_id and sql_query) with no descriptions. Schema description coverage is 0%, and the description does not explain what these parameters mean or how to use them. The agent cannot infer the expected format or purpose of each parameter.

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 the tool's function: 'Execute SQL query on a SkySQL database instance and return the results.' It uses a specific verb ('Execute') and identifies the resource (SQL query on a SkySQL instance), which distinguishes it from sibling tools that manage services or agents.

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 alternatives. There is no mention of prerequisites, context, or exclusions. For instance, it doesn't clarify whether this is for read-only queries or DDL/DML, or when to prefer ask_agent or list_services.

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