DeleteLocalMacros

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

With no annotations, the description carries the full burden. It discloses that the tool manages lock, update, unlock, and optional activation, giving insight into side effects. The version note also indicates potential incompatibility on newer systems.

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 very concise: two sentences that first state the purpose, then the process and a key note. No redundant information; every sentence 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?

Given the tool's complexity (deletion with locking and activation), the description covers the main steps. It lacks mention of return values, prerequisites, or error conditions, but the schema covers parameters well. The version note adds important context.

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?

All parameters are described in the schema (100% coverage), so baseline is 3. The description adds value by linking 'optional activation' to the activate_on_delete parameter, clarifying its role in the behavior.

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 the tool deletes local macros from an ABAP class by clearing the macros include. It distinguishes from sibling delete tools (e.g., DeleteLocalDefinitions, DeleteLocalTestClass) by specifying the resource (macros).

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 note about version support ('Macros are supported in older ABAP versions but not in newer ones') provides context for when to use the tool, implying it should be used on classes that still have macros. It does not explicitly compare with alternatives, but the purpose is clear.

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