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 full burden for behavioral disclosure. The description only states what the tool does ('check if exists') without revealing any behavioral traits such as what 'exists' entails (e.g., active configuration, user permissions), whether it's a read-only operation, potential side effects, or error conditions. This leaves critical behavioral aspects unspecified.

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, direct sentence with no wasted words: 'Check if transport configuration exists'. It's front-loaded with the core action and target, making it highly efficient and easy to parse. Every word contributes to understanding the tool's purpose.

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's simplicity (0 parameters, no output schema, no annotations), the description is minimal but incomplete. It lacks context on what 'transport configuration' refers to, what 'exists' means (e.g., configured vs. active), and what the output might indicate (e.g., boolean, status code). Without annotations or output schema, the description should provide more behavioral and result context to be fully helpful.

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 tool has 0 parameters with 100% schema description coverage, so the schema fully documents the absence of inputs. The description doesn't need to add parameter semantics, but it implicitly confirms no inputs are required by describing a simple existence check. This aligns well with the schema, justifying a baseline score of 4 for parameter clarity.

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 'Check if transport configuration exists' clearly states the action (check) and target (transport configuration), but it's somewhat vague about what 'exists' means in this context. It doesn't distinguish this tool from sibling tools like 'getTransportConfiguration' or 'transportConfigurations', which might provide more detailed information about transport configurations.

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. With sibling tools like 'getTransportConfiguration' and 'transportConfigurations' available, there's no indication whether this tool is for quick existence checks, permission verification, or other specific contexts. The user must infer usage from the tool name alone.

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