GetDomainVersionSource

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

Description declares read-only behavior with '[read-only]', but does not disclose what the returned 'source' contains (e.g., source code, metadata) or any other behavioral traits. No annotations supplement.

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, no wasted words, front-loaded with read-only indicator. Efficient and clear.

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?

Lacks description of return format or data structure, which would be helpful given no output schema. Adequate for a simple read fetch but could be more complete.

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 provides full description of 'content_uri' ('Opaque content_uri taken from a GetDomainVersions entry.'). The tool description adds no extra meaning beyond restating this.

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?

Clearly states verb 'fetch', resource 'source of a specific ABAP domain version', and how to identify the version via 'content_uri (taken from a GetDomainVersions entry)'. Differentiates from sibling Get*VersionSource tools by specifying the object type.

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?

Implies usage after GetDomainVersions to retrieve source for a specific version, but no explicit guidance on when to use this vs other version source tools, nor when not to use it.

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