GetTableVersionSource

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

Opens with '[read-only]' explicitly marking the operation as safe and non-destructive. With no annotations provided, the description carries the full burden and adequately signals no side effects beyond fetching data.

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 sentence, front-loaded with critical '[read-only]' marker, every word adds value. No fluff or repetition.

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?

Adequate for a read-only fetch tool with one parameter. Lacks description of return format (e.g., 'returns the source code as a string'), but this is consistent with other Get*VersionSource siblings and does not hinder 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?

Schema coverage is 100% with description already explaining the parameter as 'Opaque content_uri taken from a GetTableVersions entry.' The tool description repeats this but adds no new meaning beyond what the schema provides. 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?

Explicit verb 'fetch', resource 'source of a specific ABAP table version', and method 'by its content_uri (taken from a GetTableVersions entry)'. Clearly distinguishes from sibling Get*VersionSource tools which target different resource types.

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?

States prerequisite: 'taken from a GetTableVersions entry', indicating when to invoke. Does not explicitly state when not to use or mention alternatives, but the sibling context implies this is the correct tool for retrieving a table version's source after obtaining its content_uri.

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