Run ABAP Unit Tests

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

The description only says 'run' and 'return structured results', offering no insight into side effects or behavioral details. While annotations indicate non-read-only, non-destructive, and non-idempotent, the description does not clarify what state changes occur, which is critical for a mutation 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 description is very short (one sentence), which is concise but sacrifices necessary detail. It lacks any structural elements like bullet points or sections to organize information.

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?

Given no output schema and zero parameter descriptions, the description is insufficient for an agent to fully understand the tool's inputs, outputs, and behavior. Key aspects like detail levels and connection handling are omitted.

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 0% schema description coverage, the description must explain parameters but only indirectly references objectName via 'exact repository object'. The detailLevel enum and connectionId are entirely undocumented, leaving the agent without crucial semantics for correct invocation.

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 action ('Run'), the resource ('SAP ABAP Unit'), and the target ('exact repository object'). It distinguishes from sibling tools like run_atc_analysis and run_abap_application which serve different purposes.

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 provides no guidance on when to use this tool versus alternatives, nor does it mention any prerequisites or exclusions. The only implicit hint is 'exact repository object', but it fails to elaborate on context.

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