DeleteInterface

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

Discloses that a deletion check is performed before actual deletion, adding behavioral context beyond the name. However, with no annotations, it does not mention irreversibility, authorization needs, or side effects.

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 concise sentences with no extraneous text. Front-loaded with the main action and immediately clarifies a key behavioral aspect.

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?

Covers the main aspects: deletion check and transport request optionality. Missing output description but acceptable for a simple deletion tool without an output schema.

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%, and the description repeats schema info about transport request optionality without adding new semantic meaning beyond the schema itself.

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' specifying the action and resource. Distinguishes from sibling delete tools by naming the specific object type and includes mention of a deletion check.

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?

Mentions transport request optionality for $TMP objects, implying usage context but does not explicitly state when to use this tool versus other delete tools or provide when-not-to-use conditions.

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