ListFunctionModules

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

Without annotations, the description carries the burden. It states '[read-only]' implying safe reading, but no details on required permissions, pagination, or potential performance impact. Minimal disclosure beyond basic safety.

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?

Single sentence efficiently conveys the purpose and read-only nature. No filler. Well-structured for quick understanding.

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 simple listing tool with one parameter, the description is adequate. It does not describe output format, but given the tool's clarity and no output schema, it is mostly complete. Slight gap in not mentioning what the list contains (e.g., names only).

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 coverage is 100% as the only parameter is described. The description adds no further meaning to the parameter beyond what the schema provides, so baseline 3 is appropriate.

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 clearly states the tool's purpose: listing function modules of an ABAP function group. The verb 'List' and resource 'function modules' are specific. It distinguishes from sibling tools like ListFunctionGroupIncludes (lists includes) and GetFunctionModule (gets a specific module).

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. The description only notes it is read-only but does not specify context, prerequisites, or compare with siblings like GetFunctionModule or ListFunctionGroupIncludes.

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