GetTableContents

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

The description explicitly labels the tool as '[read-only]' in the first word, which is a key behavioral trait. However, with no annotations provided, it does not disclose other important behaviors such as performance implications, authentication requirements, or the meaning of the 'acknowledge_risk' parameter for tiered tables.

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 two sentences, front-loaded with the read-only tag and the core action. Every word is necessary, with no redundancy or fluff.

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 no output schema, the description explains that it returns rows of data, which is sufficient. It covers the basic purpose and read-only nature. However, it could benefit from explaining the acknowledge_risk parameter's role and the tier system, which are not addressed.

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%, with each parameter having a clear description (table_name, max_rows, acknowledge_risk). The description adds minimal value beyond the schema, only providing the SE16/SE16N analogy which indirectly gives context. Baseline 3 is appropriate.

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 verb 'Retrieve', the resource 'contents of an ABAP database table or CDS view', and the action 'data preview'. It distinguishes from sibling tools like GetTable (structure) by specifying 'contents' and the analogy to SE16/SE16N.

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 implies usage for data preview via the SE16/SE16N analogy, but does not explicitly state when to use this tool versus alternatives like GetTable or ReadTable. No exclusions or alternative recommendations are provided.

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