deleteObject

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

Annotations are absent, so description must fully disclose behavioral traits. It states only 'Deletes' without mentioning permanence, prerequisites (lock handle already in schema but not clarified), or side effects (e.g., dependencies, triggering transports). Insufficient for a destructive tool.

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?

A single, concise sentence that fully communicates the tool's purpose with zero unnecessary words. Well-structured and front-loaded.

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 destructive tool with no output schema, a minimal description should at least hint at success/failure signals or confirmation requirements. The current description meets minimum viability but lacks completeness regarding return values or post-deletion state.

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 already describes all 4 parameters with 100% coverage. Description adds no additional parameter-level detail beyond repeating 'Deletes an ABAP object'. Baseline of 3 applies as description does not degrade but also does not enhance.

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?

Description clearly states the action ('Deletes') and resource ('ABAP object'). The name 'deleteObject' reinforces this. However, it does not differentiate from similar sibling tools like 'fixEdits' or 'createObject' in terms of scope or effect.

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?

No guidance on when to use this tool versus alternatives (e.g., whether there are soft-delete or undo options, or if other deletion methods exist). The description lacks context for appropriate usage scenarios.

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