sap_read_table_data_enhanced

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

With no annotations, the description carries the behavioral burden and does reasonably well: it discloses ABAP WHERE syntax support, field validation against table structure, and the audit_mode all-records behavior. It leaves out pagination/default row limits and return shape, but those gaps are less critical for a clearly read-oriented query tool.

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 compact, front-loaded with the core action, and every sentence earns its place: examples, syntax support, audit behavior, validation, and a field-discovery prerequisite. There is no filler or repetition.

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 table-read tool with no output schema and no annotations, it covers a lot: what kinds of data, filter syntax, validation, and audit mode. It is incomplete because it does not route the agent among the similar sibling read tools, nor reconcile the missing parameter schema, so the agent still needs external help to call it correctly.

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 description adds meaning by naming audit_mode=true and field_list/WHERE clause behavior, but the input schema is literally empty, so none of these are expressed as callable properties and no table-name parameter is defined. An agent reading this description could guess the intent but cannot construct a valid invocation from the definition.

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 opens with a clear verb+resource ('Query data from an SAP table') and adds concrete SAP table examples, so an agent knows what it operates on. It does not explicitly contrast itself with sibling tools such as sap_read_table_data or sap_read_table_paginated, so it stops short of a full 5.

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?

It gives useful usage context: optional WHERE filtering, audit_mode for ALL records, and a recommendation to call sap_get_field_metadata or sap_read_table_structure first. It never states when this enhanced read should be chosen over the many sibling table-read tools or when it should not be used.

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