DeleteDomain

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

With no annotations, the description partially discloses behavior: it mentions a deletion check before actual deletion and transport request optionality. However, it omits details like reversibility, authorization requirements, error handling, or impact on dependent objects.

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 extremely concise with two sentences, no redundant information, and all sentences contribute necessary context. It is front-loaded with the main action.

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 simple delete operation and no output schema, the description covers the essential action, safety check, and parameter guidance. It lacks details on return values or error scenarios, but these are typical for delete tools and somewhat implicit.

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 adequately. The description reinforces the transport request optionality for $TMP objects, which is already present in the schema, adding marginal value.

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 an ABAP domain') and the resource type, distinguishing it from other Delete* sibling tools which target different SAP objects. It provides specific context (deletion check, transport request for $TMP objects) that reinforces purpose.

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 hints at when the tool is appropriate (e.g., includes deletion check, transport optional for local objects) but does not explicitly state when to use this tool over alternatives like CheckDomain or deactivation. No prerequisites or conditions for use are given.

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