abap_test

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

Annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, so the safety profile is covered. The description adds a confusing claim that the tool is 'LOCKED,' that calling it 'returns a refusal,' and that no request is sent — which reads as behavior but contradicts the stated purpose of running tests, and gives no coherent account of what actually happens.

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 statement is front-loaded, but it is followed by several garbled sentences about ABAP_ALLOW_WRITE, ABAP_MODE and package scoping that do not clearly resolve into a single actionable meaning. Sentences like 'that variable is what decides it' have no clear antecedent, so the length is not earning 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?

There is no output schema, so the description should explain what running tests returns; instead it says the call is refused, which leaves the agent unable to know the actual outcome. For a zero-param tool with rich annotations, the description needed to clarify invocation behavior and it does the opposite.

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 tool takes zero parameters, so per the rubric the baseline is 4. Schema coverage is reported at 100% with no properties to document, and the description introduces no parameter concepts beyond environment variables that are not inputs.

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 opening sentence names a specific verb and resource ('Run ABAP Unit tests and report each method's verdict'), which is clear enough. But the remainder muddles it badly: it claims calling the tool 'returns a refusal and sends nothing to the SAP system,' leaving the agent unsure whether the tool actually runs anything. It also doesn't distinguish this from siblings like abap_bopf_test or abap_atc.

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?

The description references config variables (ABAP_ALLOW_WRITE, ABAP_ALLOW_PACKAGES, ABAP_MODE) but never states when to use this tool versus alternatives such as abap_bopf_test or abap_run. The 'guidance' is about environment toggles, not about tool selection or preconditions an agent can act on.

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