GetServiceDefinition

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

No annotations are provided, so the description carries the full burden. It does not disclose safety traits (e.g., read-only), auth requirements, or error behavior. The only behavioral detail is version support, which is already captured in the schema.

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, succinct sentence that front-loads the purpose. Every word is necessary; there is no repetition or filler.

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?

Despite the low complexity (2 params, no nested objects), the description is incomplete because it does not explain the return value. Without an output schema, the agent needs to know what the tool returns (e.g., source code). Error cases and prerequisites are also omitted.

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%, so baseline 3. The description adds minimal value by summarizing the version parameter capabilities, but the schema already provides the same information. No additional meaning is added beyond what is in 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 action 'Retrieve' and the resource 'ABAP service definition definition'. It mentions support for active/inactive version, which helps distinguish from siblings like ActivateServiceDefinition. However, it does not explicitly differentiate from other Get* tools like GetServiceBinding, and the phrase 'definition definition' is slightly redundant.

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?

No guidance is provided on when to use this tool versus alternatives such as ActivateServiceDefinition or CheckServiceDefinition. The description does not exclude scenarios or mention prerequisites. Usage is only implied by the verb 'Retrieve'.

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