sap_read_table_data

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

There are no annotations, so the description carries the full behavioral burden. It discloses the non-obvious confirmation flow: >1000 rows returns 'requires_confirmation' with a preview and requires a follow-up call with confirmed=true. It also signals read-only semantics via 'Reads,' though it does not describe return structure or pagination.

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?

Two short paragraphs are tightly scoped: purpose and size guidance first, followed by the critical confirmation rule. Every sentence earns its place, and there is no redundant filler.

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 read tool with six parameters, no annotations, and no output schema, the description covers the key operational nuance: the 1000-row confirmation contract. It would be slightly stronger if it explicitly pointed to paginated or streaming siblings for large datasets, but the provided guidance is adequate for correct invocation.

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 schema already documents all six parameters. The description adds only high-level mention of WHERE filtering and metadata inclusion, which overlaps with the schema rather than adding deeper parameter semantics.

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?

'Reads actual data from a SAP table' pairs a precise verb with a concrete resource and clearly states optional filtering and metadata behavior. The 'small to medium datasets' scope differentiates it from larger-volume siblings like sap_read_table_paginated and sap_stream_table_data.

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 gives an explicit use condition ('small to medium datasets, up to a few thousand rows') and a required workflow for >1000-row results. It does not name alternative sibling tools for larger datasets, so the when-not-to-use guidance is only implied rather than explicit.

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