ABAP-ADT-API MCP-Server

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. 'Releases a transport' implies a mutation operation, but it doesn't describe what 'releasing' entails (e.g., changes transport status, triggers downstream processes), potential side effects, permission requirements, or error conditions. This leaves the agent with minimal actionable context.

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 extremely concise with just three words, 'Releases a transport.', which is front-loaded and wastes no space. However, this conciseness comes at the cost of completeness, as noted in other dimensions.

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 complexity implied by parameters like 'ignoreLocks' and 'IgnoreATC', the lack of annotations, and no output schema, the description is severely incomplete. It fails to explain the tool's behavior, usage context, or what 'releasing' means in this system, leaving critical gaps for an AI agent to understand and invoke it correctly.

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 description coverage is 100%, so the schema already documents all parameters ('transportNumber', 'ignoreLocks', 'IgnoreATC') with basic descriptions. The tool description adds no additional meaning about these parameters beyond what's in the schema, such as explaining what 'locks' or 'ATC checks' are or why one might ignore them.

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 'Releases a transport' is a tautology that essentially restates the tool name 'transportRelease'. It doesn't specify what 'releasing' means operationally (e.g., making it available for import, completing a workflow step) or distinguish it from sibling tools like 'createTransport', 'transportDelete', or 'transportInfo'.

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 provides no guidance on when to use this tool versus alternatives. There's no mention of prerequisites (e.g., must be in a specific status), when not to use it, or how it differs from related tools like 'transportDelete' or 'createTransport' in the sibling list.

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