CreateClassImplementation

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

No annotations exist, so the description carries the full behavioral burden. 'Write or replace' hints at destructive overwrite of existing implementations, but nothing is said about activation side effects (auto_activate defaults true), pre-audit behavior, required authorizations, or what happens to existing code not present in the new source. This is thin for a mutation tool with zero annotation coverage.

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 short sentences with the key operation front-loaded. The second sentence largely restates the scope of the first ('method implementations' vs 'CCIMP'), so it is efficient but not entirely waste-free.

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?

A mutation tool with no annotations and no output schema should explain return/error behavior and the activation implications of the defaulted boolean flags. The description covers what is being written but leaves the agent to infer failure modes and overwrite semantics from the schema alone.

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 their defaults. The description adds no syntax, format, or sizing guidance beyond the schema (e.g. whether source_code must be complete or may be partial), so 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?

Names a specific verb+resource: writing/replacing the CCIMP include of an existing global ABAP class. The phrase 'local class implementations (CCIMP)' and 'existing global ABAP class' distinguishes it from siblings like CreateClass and DeleteLocalClass, so an agent can route correctly.

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?

The second sentence gives implied context ('use this to update method implementations for local classes'), which scopes it to the local-implementation case. However, it names no explicit alternatives (e.g. CreateClass, DeleteLocalClass, CreateClassTests) and states no when-not conditions.

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