execute_query

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

With no annotations provided, the description carries the full burden of behavioral disclosure. 'Execute any SQL command' implies action but does not mention side effects, permissions, transaction behavior, or result handling. This is especially concerning for a tool that can run arbitrary, potentially destructive SQL.

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, concise sentence with no unnecessary words. It is immediately clear in purpose and well-structured, minimizing reading time while conveying essential 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?

For a tool that executes arbitrary SQL, the description is incomplete. It lacks any mention of return values, error behavior, or safety concerns. Without an output schema or annotations, the description should compensate but does not, making it insufficient for safe and effective use.

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 schema provides a complete description of the `sql` parameter ('The full SQL query'), covering it 100%. The tool description does not add any extra parameter detail, so the baseline score of 3 applies since the schema already documents the parameter adequately.

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 a resource 'any SQL command,' clearly indicating the tool's function. It distinguishes from the sibling tool `list_oracle_tables` by covering arbitrary SQL rather than just listing tables, though it does not explicitly state this differentiation.

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. The description does not mention `list_oracle_tables` or any other tools, leaving the selection entirely to inference. There is no context about intended use cases or exclusions.

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