DeleteFunctionGroup

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

With no annotations, the description carries full burden. It discloses that a deletion check occurs before actual deletion, a useful behavioral trait. However, it does not detail irreversibility, authorization needs, or effects on dependent objects, leaving gaps in transparency.

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 extremely concise with two sentences that get straight to the point. Every word adds value: verb, object, deletion check, transport options. No redundancies or unnecessary details.

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?

Given the sensitive nature of deletion and no output schema or annotations, the description is partially complete. It includes a check step and transport guidance, but misses prerequisites, success/failure indicators, and error scenarios. Adequate for a simple tool but not fully comprehensive.

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?

Input schema coverage is 100%, setting a baseline of 3. The description provides an example for function_group_name and clarifies transport_request optionality for $TMP, but these add little beyond the schema's existing descriptions. No significant additional semantics are introduced.

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 that the tool deletes an ABAP function group from the SAP system, using a specific verb and resource. It distinguishes itself from sibling tools like UpdateFunctionGroup and GetFunctionGroup by specifying deletion. The mention of a deletion check and transport options adds clarity.

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 implies the tool is for deleting function groups but does not explicitly state when to use it over alternatives like DeleteFunctionModule. It provides some guidance on transport request usage (optional for $TMP), but lacks exclusions or detailed context for when not to use it.

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