DeleteStructure

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

No annotations exist, so the description carries the full burden. It discloses the 'deletion check' behavior and transport request handling, but does not cover permissions, irreversibility, or side effects. It adds moderate value beyond the schema.

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 effectively convey the core action, a key behavioral feature (deletion check), and a parameter nuance. No unnecessary words; every clause contributes. Front-loaded with the main purpose.

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 simple delete tool without output schema, the description covers the essential action and a notable behavior. However, it lacks any indication of return value or success/failure indication. Given the complexity and number of siblings, a bit more detail could be warranted.

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 well-documented in the schema. The description adds context by clarifying that transport_request is optional for $TMP objects, which is not apparent from the schema alone. This provides meaningful additional meaning.

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'), the resource ('ABAP structure'), and adds specifics like 'deletion check before actual deletion' and transport request handling. This distinguishes it from sibling tools like DeleteTable.

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 implies when to use (to delete an ABAP structure) and provides a nuance about transport request optionality for $TMP objects, but it omits explicit guidance on when not to use or alternatives. With many sibling delete tools, more context would be helpful.

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