CreateFunctionModule

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

Without annotations, the description must fully disclose behavior. It mentions 'creates the function module in initial state', implying it is not active, but omits side effects, error conditions, idempotency, or required authorizations. Significant gaps remain.

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 contains redundant phrasing: 'Operation: Create. Subject: FunctionModule. Will be useful for creating function module.' These are unnecessary and add no value. The later sentence is more direct, but overall the description is not well-structured or concise.

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 complexity (siblings, no output schema, 4 parameters including a transport requirement), the description is insufficient. It does not mention the transport request requirement, the need for an existing function group, or the implications of 'initial state'. The high schema coverage partially compensates, but complete context is lacking.

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?

The input schema has 100% description coverage, so the baseline is 3. The tool description adds no additional parameter meaning beyond the schema's existing descriptions. It neither enhances nor detracts, meeting the baseline.

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 states 'Create a new ABAP function module within an existing function group', which clearly specifies the verb, resource, and context. However, it does not differentiate from sibling tools like CreateFunctionGroup or UpdateFunctionModule, which are distinct but not explicitly contrasted.

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. It does not mention that the function group must exist, nor does it distinguish from ActivateFunctionModule or UpdateFunctionModule. The description lacks any 'when-not-to-use' or prerequisite information.

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