GetProgramVersionDiff

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

No annotations exist, so the description carries the full burden, and it does substantial work: declares [read-only], states the exact return shape (unified diff of sources), and discloses the non-obvious batch-mode contract (call is recorded under the next number, answer is empty, read back by number after the batch ends). It does not cover failure behavior for invalid or mismatched content_uris, size limits, or whether the diff is truncated.

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?

Two sentences, front-loaded with the read-only marker and the core comparison behavior, with the batch contract trailing. The 'Recordable:' phrasing is internal jargon and the second sentence is dense, but 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 2-parameter tool with a fully documented schema and no output schema, the description covers purpose, inputs' origin, and return content. The remaining gap is practical usage detail: how to discover the content_uris and what happens when the versions are identical or the URIs are stale.

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%, and the schema itself already labels content_uri_from as the OLD/base version and content_uri_to as the NEW/compare version. The description only echoes that these are version-history entries, adding no syntax, format, or sourcing detail beyond the schema, so the baseline 3 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?

States a specific verb and resource (compares two ABAP program versions) and names the return value (unified diff of their sources). The 'ABAP program' qualifier cleanly separates it from sibling diff tools such as GetClassVersionDiff, GetInterfaceVersionDiff, GetTableVersionDiff, and GetStructureVersionDiff.

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?

It implies the workflow prerequisite by describing the inputs as 'entries of its version history', pointing an agent at GetProgramVersions/GetProgramVersionSource, and it explicitly explains how the tool behaves inside a batch. It never states when to prefer this over the generic GetObjectVersionDiff or when not to use it, so it stops short of full routing guidance.

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