GetSqlQuery

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

The description marks the tool as read-only, but omits behavioral details such as permission requirements, impact of large queries, and the significance of the acknowledge_risk parameter beyond what is in 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 a single efficient sentence with a useful read-only prefix and clear usage scope.

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?

Despite full schema coverage, the description does not explain output format, error handling, or query execution limits, leaving important gaps for a SQL execution 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 description coverage is 100%, so the description adds no extra semantic value beyond what is already in the input schema.

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 executes ABAP SQL SELECT queries on database tables and CDS views, distinguishing it from sibling tools that retrieve specific object details. It mentions specific use cases like row counts and filtered queries.

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?

The description includes a read-only tag and suggests use for ad-hoc retrieval, but does not explicitly contrast with siblings (e.g., GetTableContents for direct table access without SQL). It lacks explicit when-not-to-use guidance.

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