DeleteFunctionGroup

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

Without annotations, the description must disclose behavioral traits. It mentions a deletion check before actual deletion, which adds transparency, but it does not describe potential side effects, destructiveness, or required authorizations. The transport request optionality is helpful but incomplete for a mutation 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 concise sentences, front-loaded with the primary purpose, and then a supplementary detail. No wasted 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 is adequate for a simple delete tool but lacks information about return values, error handling, or prerequisites (e.g., the object must exist, user must have authorization). Given the number of sibling delete tools, more contextual cues would help the agent decide when to invoke this specific tool.

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%, so the schema already documents both parameters. The description adds context about transport request optionality for $TMP objects, which provides some additional meaning beyond the schema, but it does not elaborate on function_group_name beyond its name.

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 specific resource ('ABAP function group'), and includes a notable detail ('Includes deletion check before actual deletion'), which distinguishes it from other delete tools for different 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?

The description provides some usage guidance by mentioning that the transport request is optional for $TMP objects, but it does not explicitly state when to use this tool versus alternatives like DeleteFunctionModule, nor does it give conditions or prerequisites (e.g., object existence, permissions).

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