ListFunctionModules

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

No annotations are provided, so the description carries the full disclosure burden. It does self-declare '[read-only]', which is a useful trait, but says nothing about return shape, ordering, empty-result behavior, or error conditions on an unknown function group.

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?

A single efficient sentence with the read-only marker front-loaded. Nothing is wasted and nothing is buried.

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?

For a one-parameter list tool with no output schema, the definition is minimally sufficient but thin: it never hints at what the returned entries contain (module names only vs. signatures) or how results are ordered, which an agent may want before choosing it over GetFunctionModule.

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% with a single self-documenting parameter (function_group_name), so the schema already carries the semantic load. The description adds no syntax, format, or case-sensitivity detail beyond what the schema provides.

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 of an ABAP function group), so the agent knows exactly what it returns. However, it does not distinguish itself from close siblings like ListFunctionGroupIncludes or GetFunctionModule, leaving the boundary to inference.

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 versus the many sibling list/get tools (e.g., ListFunctionGroupIncludes, GetFunctionGroup, GetFunctionModule). The agent must infer the context entirely from the tool name.

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