DeleteView

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

Discloses a deletion check before actual deletion and transport request optionality. However, no annotations are provided, and the description does not mention side effects, authorization needs, or return behavior. Some transparency but gaps remain.

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, no fluff. Every word is informative and earns its place.

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 with no output schema, the description covers key aspects: what it does, the safety check, and parameter behavior. Lacks mention of return value or success confirmation, but these are minor given the tool's simplicity.

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 descriptions are already clear. The description adds a note about transport request for $TMP objects, which reinforces the schema but does not add new meaning. 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 the action (delete), resource (ABAP view), and includes additional detail (deletion check, transport request optional). It distinguishes from sibling deletion tools for other resources.

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?

Clear context for usage (deleting an ABAP view) and parameter guidance (transport request optional for $TMP objects). Does not explicitly exclude alternatives, but the purpose is specific enough.

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