CreateClassTests

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

No annotations are provided, so the description carries the full behavioral burden. It states 'create or replace' but doesn't disclose what happens to existing test classes (overwrite), whether backups are needed, activation side effects, or permission requirements. The schema parameters hint at these, but the description adds no behavioral context beyond the verb.

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 states the action and target. No wasted words.

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 is thin. It omits key context like the replace/overwrite behavior, activation implications, and how it relates to sibling tools. The rich schema covers parameters, but the description doesn't compensate for the lack of behavioral guidance.

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 five parameters are documented in the schema with defaults and meanings. The description adds no parameter details, which is acceptable given the high coverage. Baseline 3 is appropriate.

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+resource: 'Create or replace test classes within an existing global ABAP class'. The 'or replace' behavior is useful clarity. It doesn't explicitly differentiate from siblings like CreateClass or GetClassTests, but the resource (test classes) is narrow enough to be understandable.

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?

No guidance on when to use this versus alternatives like CreateClass, RunClassTests, or GetClassTests. The description doesn't mention prerequisites such as the parent class already existing, even though the schema notes it. An agent gets no routing help.

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