List ABAP Quick Fixes

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, covering safety. The description adds 'bounded non-dialog', which implies pagination (via limit/startIndex) and no interactive prompts—useful behavioral context beyond annotations. However, it does not describe response structure or error behavior.

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 a single, front-loaded sentence with no redundant words. Every word contributes: 'List' states the action, 'bounded' and 'non-dialog' add important scope, and 'SAP quick fixes' names the resource.

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?

With 6 parameters and no schema descriptions, the description is too sparse to fully guide an agent on how to use the tool. The output schema and annotations cover safety and return shape, but the description should clarify what a quick fix is and how location parameters like line, column, and startIndex relate. The qualifiers 'bounded' and 'non-dialog' are helpful but insufficient.

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 0% and the description does not explain any of the 6 parameters. It does not compensate for the lack of parameter descriptions in the schema. The parameter names are somewhat self-explanatory, but the description adds no meaning beyond what is already in 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 description states the verb 'List' and the resource 'SAP quick fixes', making the tool's purpose clear. The qualifiers 'bounded' and 'non-dialog' add scope and help distinguish it from sibling semantic tools like sap.semantic.complete or sap.semantic.documentation.

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?

There is no guidance on when to use this tool versus alternatives. It does not mention file positions, system context, or related semantic tools, leaving the agent without context for selection.

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