sap_rfc_read_table

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

With no annotations, the description carries the full burden. It discloses the underlying mechanism (RFC_READ_TABLE over SOAP), authentication (Basic Auth), and statelessness (no session). However, it does not describe return format, error handling, or potential side effects, which are notable gaps for a read operation without an output 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 two sentences, opening with the core purpose and followed by a concise feature list. Every word adds value; no redundant or filler content.

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?

The tool has moderate complexity (5 params, no output schema). The description covers key aspects like filtering, pagination, and auth, but omits the shape of the returned data, which a user might need to know to integrate with the tool. Given the lack of an output schema, this is a notable gap.

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 input schema already provides descriptions for all five parameters (100% coverage), so the baseline is 3. The description reinforces the purpose of fields, where, max_rows, and row_skips at a high level but adds no new per-parameter detail beyond what the schema offers.

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's function: reading data from any SAP transparent database table via RFC_READ_TABLE over SOAP. It enumerates specific capabilities (field selection, WHERE filters, row limits, offsets) and distinguishes itself from siblings by noting it requires no session and uses Basic Auth directly.

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 provides clear context for when to use the tool ('No session required — uses Basic Auth directly'), implying it is suitable when no SAP session exists. However, it does not explicitly mention when to avoid it or name alternatives among siblings (e.g., sap_se16_browse), leaving usage guidance partially implied.

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