UpdateFunctionGroupUnitTest

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

With no annotations, the description must carry the behavioral load. It does disclose two useful traits: the existing test classes are REPLACED (destructive overwrite) and the include is ACTIVATED as a side effect. It says nothing about permissions, transport/authorization requirements, or failure behavior when the include is missing.

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 leads with the verb and resource before the scoping detail. No filler, though the trailing 'and activate it' clause could be slightly more clearly framed as a side effect.

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 the core action and its two key side effects but omits preconditions and side-effect specifics (transport need, permission requirements, behavior on a missing test include). Since the schema already documents parameters fully, this is minimally sufficient but not rich.

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 documents all four parameters, including transport_request and the detail enum. The description only loosely maps to test_class_source ('replace the local test classes') and adds no syntax or format 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?

The description gives a specific verb+resource ('Update the ABAP Unit tests of a function group') and adds concrete scope ('replace the local test classes in its test include and activate it'), which distinguishes it from siblings like CreateFunctionGroupUnitTest and UpdateLocalTestClass. It does not name those siblings outright, but the resource and operation are unambiguous.

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 implied rather than stated: the operation clearly applies to an existing function group whose test include already exists, but there is no explicit when-to-use/when-not guidance or routing to alternatives such as CreateFunctionGroupUnitTest or UpdateLocalTestClass. Adequate but with a clear gap.

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