GetStructureVersionSource

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

The description includes '[read-only]' tag upfront, disclosing the non-destructive nature. With no annotations, it effectively communicates the safe read behavior, though it does not detail return format or potential errors.

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 with 15 words, front-loaded with the [read-only] tag. No wasted words; every part 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 simple one-parameter read-only tool with full schema coverage, the description adequately explains what it does and the input source. It does not describe the output, but given no output schema, that is a minor gap.

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%. The description adds value by clarifying the parameter is 'opaque' and linking it to a GetStructureVersions entry, going beyond the schema's 'Opaque content_uri' description. This provides practical usage context.

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' and the resource 'source of a specific ABAP structure version', specifying the input 'content_uri' from a prior call. It distinguishes itself from sibling tools like GetStructureVersionDiff and GetStructureVersions.

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 instructs to take the content_uri from a GetStructureVersions entry, providing clear prerequisite context. It does not explicitly mention when not to use, but the requirement of a prior call implicitly limits usage.

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