CreateFunctionGroup

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

Mentions 'Uses stateful session for proper lock management' which is a behavioral detail. However, no annotations exist, so description carries full burden. Does not disclose side effects (creates object), permissions needed, or idempotency. Lacks important behavioral traits for a write 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?

Three short sentences with no fluff. Front-loaded with purpose. Could be slightly more structured (e.g., bullet-point key usage), but overall efficient.

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?

Lacks details about return values (no output schema), confirmation of success, or failure behavior. For a creation tool with 6 parameters and no annotations, the description should provide more context about the outcome and dependencies (e.g., transport request requirement highlighted).

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?

Description provides no additional meaning beyond the 100% schema-covered parameters. Baseline 3 is appropriate because the schema already documents all parameters adequately.

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 'Create a new ABAP function group' and explains its role as container for function modules. Distinguishes from siblings like UpdateFunctionGroup and DeleteFunctionGroup via the verb 'Create'.

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 when-to-use or when-not-to-use compared to other Create* tools. Usage is implied by the tool name, but no guidance on prerequisites (e.g., transport request required for transportable packages) or alternatives.

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