CreateFunctionGroupUnitTest

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

With no annotations, the description carries the full burden. It usefully discloses that the include is created together with its local test classes and that it is activated with the group, which is a real side effect. However, it says nothing about permissions, error/exception behavior, or what happens when the include already exists.

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?

A single front-loaded sentence that names the action, the target, and the resulting artifact with no filler. It could have gone marginally further on lifecycle behavior, but every clause earns 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?

For a mutation tool with no annotations and no output schema, the description covers what is created and that it is activated, and the 100%-covered schema handles parameters. It omits conflict/overwrite behavior and any indication of what a caller gets back, leaving meaningful gaps for an agent invoking a write operation.

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 all four parameters are already documented (including that test_class_source replaces the include contents and that transport_request is required for transportable objects). The description only loosely maps to test_class_source and adds no format or syntax detail beyond the schema, so the baseline 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?

States a specific verb ("Create") and resource ("ABAP Unit tests for a function group") and even describes the artifact produced: a test include with local test classes. This distinguishes it in substance from CreateUnitTest and UpdateFunctionGroupUnitTest, though it never names those siblings to route the agent explicitly.

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 explicit when-to-use or when-not-to-use guidance and no named alternative. The agent must infer from context that this is for function groups rather than the CreateUnitTest / CreateCdsUnitTest siblings, and the description offers no condition to select between them.

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