DeleteFunctionModule

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

Adds that a deletion check is performed before actual deletion, which is a useful behavioral trait. However, with no annotations, the description carries full burden and omits other important behaviors such as authorization requirements, reversibility, or side effects on dependencies.

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 covering purpose, behavior, and parameter nuance with no redundancy. Front-loaded with the main action.

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?

Adequately covers the core deletion action and check, but missing broader context such as error conditions, locked objects, or implications for dependent objects. Given lack of annotations and output schema, more detail would be beneficial.

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 baseline is 3. The description does not add meaning beyond what the schema already provides for the parameters. Transport request optionality is already in the schema description.

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?

Clear verb 'Delete' and resource 'ABAP function module' with additional context about deletion check and transport. Distinguishes from sibling Delete* tools by specifically targeting function modules.

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 explicit guidance on when to use this tool vs alternatives like DeleteFunctionGroup. The description mentions transport request optionality but does not compare with other delete tools or provide decision criteria.

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