CreateFunctionGroupUnitTest

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

With no annotations, the description carries the burden and does disclose non-obvious behavior: the classes go into a test include that is activated along with the group, and the operation runs outside batch mode. It omits permissions, transport behavior, and reversibility, but the key side effects are stated.

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?

Three compact sentences with the target object and inputs front-loaded, then the persistence/activation behavior, then the batch-mode constraint. No filler.

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 destination, activation behavior, and an execution constraint. It does not describe what the call returns (implied only by the detail parameter enum), which is a minor gap given 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 all four parameters are already documented in the schema (including the detail enum and the transport_request note). The description only restates that function_group_name names the group and test_class_source supplies the source, adding no syntax or format detail beyond the schema.

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 and resource: creating ABAP Unit test classes for a named function group from source. The mention of the test include and activation makes it clearly distinct from CreateUnitTest/CreateProgramUnitTest, though it doesn't explicitly name those siblings as alternatives.

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?

Usage is only implied by the create-vs-update naming (UpdateFunctionGroupUnitTest exists as a sibling) and by the schema note that the function group must already exist. No explicit when-to-use, ordering (e.g., after CreateFunctionGroup/ActivateFunctionGroup), or alternative is stated in the description.

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