DeleteMetadataExtension

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

With no annotations, the description must disclose behavior. It mentions a deletion check before actual deletion, which adds behavioral insight. But it does not cover authorization needs, reversibility, or side effects, leaving gaps for a delete operation.

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, front-loaded with the core action. No superfluous words. Every phrase 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?

For a simple delete tool with two parameters, no output schema, and no nested objects, the description is fairly complete. It covers the main action, a safety check, and parameter optionality context. Some minor behavioral details (e.g., error handling) are missing, but not critical.

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 description coverage is 100% with detailed descriptions for both parameters. The tool's description adds minimal additional parameter info ('Transport request optional for $TMP objects') which is already in the schema. Nothing beyond the schema is provided.

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 that the tool deletes an ABAP metadata extension, using a specific verb ('Delete') and resource ('ABAP metadata extension'). Distinguishes from sibling delete tools by naming the exact object type. Includes additional detail about 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?

Provides some context by noting that transport request is optional for $TMP objects, implying usage conditions for different object types. However, it does not explicitly state when to prefer this over other delete siblings or mention any prerequisites or alternatives.

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