DeleteLocalDefinitions

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

In the absence of annotations, the description reveals that the tool manages lock, update, unlock, and optional activation, indicating a transactional operation. However, it does not disclose side effects, error handling, or reversibility, which are important for a delete operation.

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?

The description is a single concise sentence that front-loads the core action. It includes relevant procedural details but could be slightly more structured, though it is not overly verbose.

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?

Given the high number of sibling tools and no output schema, the description lacks completeness. It does not differentiate from similar tools or explain return values, making it harder for an agent to select correctly.

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?

The input schema already covers all three parameters with descriptions, so the baseline is 3. The description adds only marginal value by hinting at the activate_on_delete parameter ('optional activation'), but does not elaborate on how parameters relate to the operation.

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 clearly states 'Delete local definitions from an ABAP class' with the specific verb 'Delete' and resource 'local definitions'. It also explicitly mentions clearing the definitions include, which differentiates it from sibling tools like DeleteLocalMacros or DeleteLocalTestClass.

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 description provides no guidance on when to use this tool versus alternatives such as UpdateLocalDefinitions or other delete tools. It lacks context about prerequisites or scenarios where it should be avoided.

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