GetFunctionGroupVersions

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

Declares read-only and lists returned fields (versionId, author, etc.) and the opaque content_uri. Adds value beyond annotations (none provided). Could mention pagination or sorting, but sufficient for a simple list.

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 clear front-loading ([read-only] and purpose). Includes necessary details without waste.

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?

Tool is simple with one parameter; description covers purpose, return fields, and links to related tool. Lacks error handling or limitations, but adequate for selection.

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 has one param with good description (100% coverage). Description reinforces 'ABAP function group name', adding context. Slightly above baseline 3.

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?

Clear verb 'List' and resource 'SAP version history of a ABAP function group'. Distinguishes from siblings GetFunctionGroupVersionDiff and GetFunctionGroupVersionSource by mentioning content_uri links to the latter.

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: list versions then fetch source via GetFunctionGroupVersionSource. Lacks explicit when-not-to-use or alternatives, but provides enough context for an agent to decide.

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