GetDataElementVersionSource

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

The description marks the tool as [read-only] upfront, clarifying it is non-destructive. Since no annotations are provided, this disclosure is crucial. It does not detail authorization or error conditions, but the read-only tag provides sufficient transparency for a fetch operation.

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, focused sentence with no redundancy. It front-loads the read-only tag and immediately conveys the action, resource, and required input.

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?

Given the simple nature of the tool (one parameter, no output schema, read-only), the description is complete. It explains what the tool does, how to obtain the required parameter, and that it has no side effects.

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 input schema already provides a full description for content_uri (100% coverage), so the tool description adds minimal extra value. However, the description reinforces the source of the URI (from GetDataElementVersions) and its 'opaque' nature, which adds contextual meaning beyond the schema.

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 the verb 'Fetch', the resource 'source of a specific ABAP data element version', and specifies the required input 'content_uri' from a prior GetDataElementVersions call. It distinguishes from sibling version source tools by referencing 'data element'.

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 explicitly states the prerequisite that the content_uri must come from GetDataElementVersions, guiding the agent on when to use this tool. It does not mention explicit when-not scenarios or alternatives, but for a simple fetch tool this is adequate.

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