CreateProgramUnitTest

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

With no annotations, the description carries the behavioral burden well: it discloses that test classes are written to a test include, that the include is added to the report, that the report is activated, and that execution occurs outside batch mode. It still does not mention permission requirements, failure behavior, or reversibility.

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 three tight sentences, front-loads the core action and inputs, and adds only high-value behavioral details. There is no repetition or wasted text.

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?

The description supplies the key mutation side effects (test include creation, inclusion into the report, activation) and the execution mode. Given that the schema covers parameters and there is no output schema, this is largely complete, though error/overwrite semantics are only indirectly covered by the schema.

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 coverage is 100%, so the schema already documents all four parameters including the 'detail' enum and 'transport_request'. The description names program_name and test_class_source but adds no parameter meaning beyond the schema, so the baseline of 3 applies.

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 gives a specific verb ('Creates'), a specific resource ('ABAP Unit test classes of the report'), and names the key inputs ('program_name', 'test_class_source'). It also distinguishes the tool from generic unit-test creation by tying it to a report, a test include, and report activation.

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?

It states the context in which the tool operates ('of the report', 'Runs outside batch mode'), but does not explicitly say when to use it instead of siblings such as CreateUnitTest, UpdateProgramUnitTest, or RunProgramUnitTest. Usage is implied rather than routed.

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