GetFunctionModuleVersions

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

Declares read-only with '[read-only]' and lists all returned fields. Without annotations, it describes the operation well, though misses potential limitations like pagination.

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 tight sentence, front-loaded with read-only annotation, no redundant words.

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?

Covers purpose, output structure, and links to related tool. Lacks details on sorting, filtering, or error handling, but sufficient for a version list.

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%, so description adds no new meaning to parameters beyond naming. Baseline applies.

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 it lists SAP version history of a function module, including specific fields. It distinguishes itself from sibling tools like GetFunctionModuleVersionDiff and GetFunctionModuleVersionSource.

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 guidance. It implies GetFunctionModuleVersionSource for source fetching, but lacks clear direction compared to alternatives.

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