GetFunctionModuleVersionSource

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

The tool is marked [read-only], indicating no side effects, but no annotations are provided. The description does not elaborate on authentication, rate limits, or other behavioral traits beyond the read-only hint.

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?

The description is a single, concise sentence that front-loads the [read-only] tag. Every word is necessary and no redundant information is present.

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 read-only tool with one parameter and no output schema, the description fully explains the purpose and origin of the input. It is complete for an agent to invoke correctly.

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?

The single parameter 'content_uri' is described in both the schema and the description as an opaque URI from GetFunctionModuleVersions. With 100% schema coverage, the description adds useful context about the source of the URI.

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 fetches the source of an ABAP function module version using a content_uri from GetFunctionModuleVersions. It uses specific verb 'Fetch' and identifies the resource, distinguishing it from sibling tools that handle activation, deletion, or listing.

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 description explains the prerequisite of having a content_uri from GetFunctionModuleVersions, providing context for when to use this tool. However, it does not explicitly state when not to use it or mention alternatives.

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