GetFunctionGroupVersionSource

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

The description starts with '[read-only]', signaling no side effects. With no annotations provided, the description carries the burden; it adequately discloses the read-only nature but does not elaborate on permissions or error conditions.

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, well-structured sentence. It front-loads '[read-only]' and efficiently conveys the purpose and input source with no extraneous information.

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?

Given one parameter and no output schema, the description sufficiently explains the tool's function and input origin. It does not detail the return format, but agents can infer source code is returned. The context is adequate for correct invocation.

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 has a clear description in the schema. The description adds value by specifying it is 'taken from a GetFunctionGroupVersions entry', providing context beyond the schema's 'opaque' description.

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 a specific ABAP function group version, using a content_uri from GetFunctionGroupVersions. It distinguishes from similar sibling tools like GetFunctionGroupVersionDiff and GetFunctionGroupVersions by specifying the exact action (fetch source) and the input source.

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 implicitly guides usage by stating the input is taken from a GetFunctionGroupVersions entry, indicating a dependency. It provides clear context for when to use this tool, but 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.