Resolve SAP Transport Object

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

The description adds minimal behavioral context beyond what annotations already declare. Annotations state readOnlyHint=true, idempotentHint=true, and destructiveHint=false, but the description does not disclose edge cases, pagination, or output behavior. The phrase 'one SAP repository object' is mild scope limitation but not significant.

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, focused sentence that clearly states the operation. Every word contributes value, with no redundancy 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?

Given the tool has 7 parameters, an output schema, and many sibling tools, the description is too sparse. It lacks parameter semantics, usage context, and any explanation of how the resolution works, making it insufficient for an agent to invoke it correctly without additional inference.

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?

The description provides no explanation of any of the 7 parameters (systemId, pgmid, objectType, objectName, limit, startIndex, transportNumber). With 0% schema description coverage, the description must compensate but does not, leaving these parameters entirely undocumented.

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 uses a specific verb 'resolve' with a clear resource 'SAP repository object' and output 'transport key', distinguishing it from sibling tools like sap.transport.object.add or sap.repository.resolve. The scope of one object is also explicit.

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 usage guidance is provided. The description does not mention when to use this tool versus alternatives such as sap.transport.object.add or sap.repository.resolve, nor any preconditions, exclusions, or context for selection.

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