DeleteClass

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 a deletion check before actual deletion, which is a helpful behavioral detail. However, it does not mention irreversible consequences, authorization requirements, or what happens to dependent objects. The transparency is adequate but not exhaustive.

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 sentences with no superfluous words. Every sentence adds value: the first states the action, the second notes the deletion check and transport request nuance. Highly efficient.

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 no output schema and no annotations, the description covers the core operation and one conditional aspect (transport request). It lacks information about return values, failure modes, or what the deletion check returns. For a delete tool, this is adequate but not fully complete.

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 coverage is 100%, so the schema already documents both parameters. The description adds context about the transport request being 'optional for $TMP objects,' but this largely mirrors the schema description. No additional semantics are provided beyond what the schema offers, so the value added is minimal.

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 action ('Delete') and the resource ('ABAP class'), and includes the key detail of a deletion check. It distinguishes from sibling tools like CreateClass or UpdateClass by specifying the delete operation.

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 mentions that transport request is optional for $TMP objects, which guides usage. However, it does not explicitly contrast with alternatives like CheckClass (which could be used before delete) or other delete tools, so some guidance is implicit rather than explicit.

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