UpdateProgramUnitTest

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

With no annotations, the description carries the full burden and does disclose real behavioral traits: the existing local test classes in the test include are overwritten, the object is activated as a side effect, and the call cannot run in batch mode. What it omits is failure behavior (missing test include, activation failure) and any transport/permission implications, leaving a gap for a destructive mutation.

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 short sentences, front-loaded with what is written and to what; the overwrite and activation consequences follow immediately. No filler and no restatement of the title.

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 essentials: source target, overwrite scope, activation side effect, and an execution-environment constraint. It falls short only on error conditions and transport handling, which an agent would otherwise need to infer.

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 baseline is 3. The prose adds a little meaning to program_name ('the report whose tests are replaced') and test_class_source ('local test classes: definitions and implementations, FOR TESTING'), but says nothing about detail or transport_request beyond what the schema already documents.

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: writing test_class_source as the ABAP Unit test classes of the report in program_name, with the local test classes in the test include rewritten and activated. That is enough to separate it from Run/Create/Delete counterparts by name, though it never explicitly names the sibling tools it is not (CreateProgramUnitTest, UpdateLocalTestClass) to confirm the boundary.

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 context is only implied: the tool is for replacing existing local test classes of a program, and the prerequisite that the test include must already exist lives in the schema, not the description. There is no explicit statement of when to prefer CreateProgramUnitTest or UpdateLocalTestClass, and the 'runs outside batch mode' note reads as environment trivia rather than a selection rule.

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