GetClassVersionSource

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

Discloses read-only behavior upfront via '[read-only]' tag. Explains input dependency. No annotations exist, so description carries full burden; it sufficiently covers expected behavior for a simple fetch operation.

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, front-loaded sentence of 20 words with no wasted text. The read-only flag is placed at the beginning, maximizing scannability.

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?

With one parameter and no output schema, the description clearly explains what the tool does and how to obtain the input. It does not describe the output format, but for a simple source fetch this is adequate.

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% and the schema description for content_uri already states 'Opaque content_uri taken from a GetClassVersions entry.' The tool description repeats this without adding new meaning, 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?

Description clearly states the verb 'Fetch' and resource 'source of a specific ABAP class version', and specifies the input source (content_uri from GetClassVersions). It distinguishes from sibling tools like GetClassVersionDiff.

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?

Explicitly states the prerequisite: content_uri taken from GetClassVersions. Provides clear context for when to use, though does not list alternative tools for other scenarios.

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