ListFunctionModules

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

No annotations are provided, so the description carries the burden. It does disclose two traits — read-only nature and that it must run outside batch mode — but says nothing about permissions, pagination, result size, or what happens with an invalid function group name.

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 short sentences with zero waste; the [read-only] marker and the core action are front-loaded, and the batch-mode caveat is appended where it belongs.

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?

With one fully documented parameter the input side is covered, but there is no output schema and the description does not indicate what the listing returns (names only, full module metadata, ordering). For a list-style tool that gap is meaningful but not crippling.

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?

Only one parameter exists and schema coverage is 100%, so the schema already documents it. The description's phrase 'of an ABAP function group' confirms the parameter's role as the container being enumerated, adding slight clarity over the terse schema description 'Function group 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?

States a specific verb ('List') and resource ('function modules') with a clear scope qualifier ('of an ABAP function group'). An agent can distinguish it from GetFunctionModule (single object) by implication, though siblings like ListFunctionGroupIncludes are 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?

The scope phrase hints at when to use it (enumerating members of a known function group), and 'Runs outside batch mode' implicitly excludes one context. However, no alternative tool is named and no explicit when-not guidance beyond the batch-mode restriction is given.

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