sap_se16_browse

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

With no annotations, the description carries the full burden, and it does disclose two key behaviors: only the first page is returned, and the output is plain text. It does not mention authorization requirements or pagination follow-up, but for a simple read-only browsing tool this is meaningful transparency.

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 one short sentence with no filler, front-loading the core purpose and immediately stating the return behavior. Every word earns its place.

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 simple two-parameter tool with a fully documented schema, the description is sufficient for basic selection and invocation: it names the action, resource, output type, and first-page limitation. Minor gaps exist around pagination and comparison with sap_rfc_read_table, but they do not undermine basic usability.

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 baseline is 3. The description adds little parameter-specific meaning beyond the phrase 'first page,' which loosely relates to max_rows; the schema already documents both table_name and max_rows with constraints and examples.

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 ('browse'), resource ('database table'), and method ('via SE16 / Data Browser'), and it specifies the output ('first page... as text'). However, it does not explicitly differentiate this from the sibling sap_rfc_read_table, which likely also reads 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?

No guidance is provided about when to use SE16 browse versus the sibling sap_rfc_read_table, nor are preconditions or exclusions mentioned. The description implies usage only through the tool name and purpose, leaving the agent to infer selection criteria.

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