DeleteDomain

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

With no annotations provided, the description carries the full burden. It discloses a behavioral trait: 'Includes deletion check before actual deletion', which adds safety awareness. It also notes transport request optionality. No contradictions with annotations (none present).

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, front-loaded with the main purpose. Every sentence adds value: first states action, second adds safety check and transport option. No wasted words.

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?

For a deletion tool with no output schema and no annotations, the description covers the core purpose, safety check, and optional transport parameter. It lacks details on error scenarios or idempotency, but is sufficiently complete for a basic delete operation.

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 parameters are fully described. The description reinforces the transport request behavior ('optional for $TMP objects') which matches the schema. No additional parameter semantics beyond the schema are provided, 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?

The description clearly states 'Delete an ABAP domain from the SAP system', using a specific verb and resource. It distinguishes from sibling tools that delete other object types (e.g., DeleteClass, DeleteDataElement) by explicitly naming the resource type 'domain'.

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 implicitly indicates this tool is for deleting ABAP domains, and noting the transport request optionality for $TMP objects provides context. However, it does not explicitly exclude other use cases or mention alternatives, though the sibling list makes differentiation clear.

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