DeleteBehaviorDefinition

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

The description mentions a deletion check before actual deletion, which adds transparency, but lacks details on authentication requirements, side effects, reversibility, or error conditions. No annotations are provided, so the description carries full burden.

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?

The description is two sentences, front-loaded with the core action, and contains no unnecessary words. Every sentence adds value.

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?

The description covers the deletion check and transport handling, but does not mention success/failure output, error handling, or what happens after deletion. Given no output schema, some description of expected return would improve completeness.

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?

Parameter descriptions are fully covered in the schema (100%). The description adds that transport request is optional for $TMP objects, reinforcing schema info, but does not add significant new meaning beyond that.

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 behavior definition), and adds context (deletion check, transport request handling). It distinguishes from siblings like DeleteBehaviorImplementation.

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 notes optional transport for $TMP objects, but does not explicitly state when to use this tool versus other delete tools or provide prerequisites or exclusion criteria.

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