Execute ABAP Data Query

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

The description claims the tool is read-only, but the readOnlyHint annotation is set to false, which is a direct contradiction. No other behavioral details are provided beyond the claim of read-only operation.

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 concise (one sentence) and front-loads the core purpose, but it omits critical details about parameters and usage, making it insufficiently informative.

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 the tool's complexity (14 parameters, nested objects, no output schema, no parameter descriptions), the description is far from complete. It fails to clarify what 'bounded headless result' means, how to configure export or data processing, or what the parameters do.

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 0%, meaning no parameter descriptions exist. The tool description does not explain any of the 14 parameters, including nested objects like sql, data, filters, or display modes, leaving the agent without guidance.

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 runs a read-only SAP ADT data-preview query, processes supplied structured data, returns a bounded headless result, or exports to CSV/XLSX. The verb and resource are specific, and it distinguishes itself from sibling tools like abap_activate or run_sap_transaction.

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 prerequisites, limitations, or scenarios where another tool would be more appropriate.

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