sap_get_enhancements

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

With no annotations, the description carries the safety/disclosure burden. It discloses that the call lists all enhancements, that the program is resolved automatically from a transaction, and the exact fields per entry (type, name, implementation, active status, program, include name). It could go slightly further (e.g., stating read-only/no side effects), but 'List' plus the output inventory is strong for a read-oriented 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 core action is front-loaded and every sentence carries information; the keyword list and table-name exclusions are useful, not fluff. It is slightly verbose due to the repeated examples, but remains efficiently scannable.

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 two-optional-parameter tool with no output schema, the description covers the return shape, parameter examples, and scope. It does not explicitly describe error behavior when neither parameter is supplied, but the schema description covers the 'at least one' requirement.

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 coverage is 100%, so the baseline is 3, but the description adds genuine value by giving concrete examples for both parameters ('BP', 'VA01', 'XD01', 'SAPMV45A') and explaining that program resolution is automatic. It also reinforces the 'at least one required' constraint from the schema.

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 first sentence states a specific verb ('List') and resource ('enhancements for a SAP transaction or program'), and enumerates the exact artifact types returned (BAdIs, customer exits, enhancement spots, BTEs). This clearly differentiates it from sibling tools like sap_read_code or sap_read_where_used.

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?

Contains an explicit 'USE THIS when' clause listing trigger keywords (BAdIs, SMOD/CMOD, SE18/SE19, BTEs, etc.) and an explicit 'DO NOT' instruction to avoid manual table queries. That is direct selection guidance rather than leaving usage to inference.

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