GetProgramVersionSource

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

With no annotations, the description carries the behavioral burden and clearly declares that the tool is read-only. It also explains non-obvious batch behavior: the call is recorded, returns empty content, and must be read by number after the batch ends. It does not cover permission requirements or error behavior, keeping it short of full transparency.

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 two tight sentences, front-loads the read-only nature and core purpose, then adds only the relevant batch-mode caveat. No sentence is wasted.

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 single-parameter read-only getter with no output schema, the definition covers purpose, safety, and batch semantics adequately. A minor missing piece is explicit guidance to obtain content_uri from a version-history listing tool such as GetProgramVersions.

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 description coverage is 100%, so the parameter is already documented in the schema. The description reinforces that content_uri identifies an entry in the ABAP program's version history, but adds no format or sourcing detail beyond that baseline.

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 uses a specific verb ('Reads the source') and names the exact resource: the ABAP program version identified by content_uri. It clearly distinguishes itself from version-listing and version-diff siblings by focusing on retrieving source for one version.

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 implies the tool should be used when the source of a specific version is needed, but it does not explicitly say when to use it versus GetProgramVersions or GetProgramVersionDiff. The batch-mode note describes behavior rather than selection guidance.

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