unitTestRun

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

The description adds a valuable behavioral warning beyond the annotations: an empty result does not mean tests passed, but rather that no tests ran, and the answer explains why. This discloses a non-obvious result behavior that structured annotations do not convey. No contradiction from annotations.

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 two sentences, front-loaded with the action and then the critical caveat. Every sentence contributes meaningful information with no filler or repetition.

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-parameter tool with 100% schema coverage and no output schema, the description covers the most important operational nuance. It does not detail full output shape or side effects, but it provides enough context for an agent to call and interpret the action correctly.

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 100%, so the schema already fully documents the url and flags parameters. The description adds no further semantic detail about parameters, so it stays at the baseline for high schema coverage.

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 a specific verb and resource ('Run ABAP Unit tests for an object'), making the core purpose clear. It does not explicitly differentiate itself from sibling tools such as runTests or unitTestEvaluation, so it lacks explicit sibling distinction but is not vague.

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 like runTests or unitTestEvaluation, and no conditions or exclusions are stated. The main content is a result-interpretation caveat, not usage direction, so an agent gets no help choosing among sibling tools.

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