GetDomainVersions

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

Begins with '[read-only]' indicating no side effects. Lists exact return fields and notes when transport details are available. No annotations provided, so description carries burden well.

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 front-loaded with '[read-only]', contains all key information without redundancy. Efficient but dense.

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?

Explains all return fields and the purpose of content_uri. No output schema, so this is necessary. Lacks details on ordering or pagination, but acceptable for a list tool.

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?

Only one parameter domain_name with schema description 'ABAP domain name.' Description adds no further meaning. Schema coverage is 100%, so baseline 3 is appropriate.

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 the verb 'List' and the resource 'SAP version history of a ABAP domain'. Differentiates from sibling GetDomain (current version) and GetDomainVersionSource (fetch source) by explicitly mentioning the content_uri usage.

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?

Implied usage: for listing version history. References GetDomainVersionSource for fetching source, guiding further action. No explicit when-not-to-use, but context from sibling names clarifies scope.

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