DeleteInterface

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

Discloses that deletion includes a check before actual deletion, but lacks details on reversibility, authorization requirements, impact on dependencies, or return values. With no annotations, more behavioral context would be expected.

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?

Extremely concise at two sentences, front-loaded with the core action. Every word serves a purpose without redundancy.

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?

Adequately covers the core operation and a noteworthy behavior (deletion check), but lacks information about success/failure outcomes, error handling, or return values. Given the context of siblings like CheckInterface, more completeness would be helpful.

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% with descriptions for both parameters. The description adds 'Transport request optional for $TMP objects,' which is already implicit in the schema, so minimal additional 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?

Clearly states 'Delete an ABAP interface from the SAP system' with a specific verb and resource. The description adds details about a deletion check and transport request, distinguishing it from other Delete* tools.

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?

Provides context that the deletion includes a check and transport handling, but does not explicitly state when to use this tool versus alternatives like CheckInterface or UpdateInterface. No exclusions or prerequisites are mentioned.

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