GetPackageVersionSource

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

The description tags it as [read-only], indicating no side effects. With no annotations, this disclosure is helpful. It doesn't detail return format or potential errors, but for a simple read tool it is adequate.

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, front-loaded sentence with no extra words. Every part is necessary and earns its place.

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 straightforward read tool with one parameter and no output schema, the description covers the core purpose and input origin. It could be improved by hinting at the response structure, but it's largely sufficient.

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 schema already describes the parameter as 'Opaque content_uri taken from a GetPackageVersions entry.' The description repeats this without adding new semantic meaning. Baseline 3 due to 100% schema coverage.

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 it fetches the source of an ABAP package version using a content_uri from GetPackageVersions. It distinguishes from siblings which target other object 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?

It specifies the input comes from a GetPackageVersions entry, giving clear context for when to use. It does not explicitly state when not to use or list alternatives, but the parameter's source is well-described.

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