GetServiceBinding

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

No annotations are provided, so the description must fully disclose behavior. It describes the operation as a retrieval but does not explicitly state that it is read-only, non-destructive, or side-effect-free. It also omits authorization requirements or behaviors on missing names. The description offers basic transparency but lacks depth.

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, well-structured sentence that conveys the essential purpose and endpoint without extraneous detail. It is front-loaded and efficient, earning 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?

Given the tool has only 2 parameters, 100% schema coverage, no output schema, and a straightforward retrieval operation, the description is reasonably complete. It covers the action, resource, endpoint, and parameter details. Minor gaps include lack of error handling or output structure, but these are not critical for a simple getter.

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%, providing a baseline of 3. The description adds value by including an example for service_binding_name and explaining each option for response_format (json, xml, plain) beyond the enum values, aiding correct parameter selection.

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 ('Retrieve'), resource ('ABAP service binding source/metadata'), input method ('by name'), and endpoint ('ADT Business Services endpoint'). This distinguishes it from sibling tools like CreateServiceBinding or ActivateServiceBinding.

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 implies retrieval use, which contrasts with siblings for creation, deletion, or activation. However, it lacks explicit guidance on when to prefer this over other getter tools (e.g., GetServiceDefinition) or when not to use it. Context from the tool name and sibling list makes it reasonably clear.

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