ActivateClasses

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

No annotations are provided, so the description carries the full burden. It discloses the lifecycle prerequisite (class must already exist/be modified) but says nothing about side effects, idempotency, lock/permission needs, or what activation failure looks like — real gaps for a state-changing tool.

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?

Two tight sentences with the core action front-loaded and the parameter routing immediately after. 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?

With no annotations and no output schema, the description should say more about the result of activation (success/failure signal, whether it returns diagnostics). It covers the invocation contract adequately but leaves the outcome unspecified.

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 three parameters, including the class_name/class_names exclusivity that the description merely repeats. The description adds no meaning for preaudit_requested beyond what the schema states.

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 (Activate) and resource (ABAP classes) and scopes it to a lifecycle stage ('after creation or modification'), which distinguishes it from CreateClass/DeleteLocalClass. It does not explicitly name the sibling it complements, but the action is 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?

Gives clear context for when to invoke it (post-creation or post-modification) and states the mutually exclusive parameter pattern ('either class_name ... or class_names'). It stops short of naming alternatives or prerequisites such as needing an existing class first.

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