abap_quick_fix

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false. The description adds genuinely new behavior: the tool is locked on this server and calling it returns a refusal without sending anything to SAP. However, the surrounding logic is garbled ('ABAP_ALLOW_WRITE does not enable writes... so that variable is what decides it', then 'Set ABAP_ALLOW_WRITE=true'), which muddies an otherwise useful disclosure.

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 useful purpose sentence is followed by three sentences of dense, self-contradictory server-config text about environment variables. That material does not earn its place for an agent selecting a tool, and the structure front-loads a purpose it then undermines.

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 zero-parameter tool with no output schema, the description never explains how a quick fix is identified or what listing returns. Combined with the missing position parameter and the muddled lock explanation, an agent cannot tell what would actually happen or how to invoke it meaningfully.

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?

With zero parameters and 100% schema coverage, the baseline is 4. The description is downgraded because it references configuration knobs (ABAP_ALLOW_WRITE, ABAP_ALLOW_PACKAGES) and a 'source position' that appear nowhere in the empty schema, so it does not clarify the actual (absent) inputs and instead introduces entities the agent cannot supply.

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 gives a verb and resource: 'List and apply ADT quick fixes at one source position.' But the scope phrase 'at one source position' is unactionable given the schema has zero parameters, and nothing distinguishes this from siblings like abap_write, abap_enh, or abap_read. The purpose is stated but immediately buried under server-config discussion.

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 when-to-use guidance relative to alternatives, nor any exclusions. The only guidance is operational server state ('LOCKED on this server... calling it returns a refusal'), which tells the agent the tool is inert but not when to prefer this over any sibling.

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