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. 'Sets' implies a mutation/write operation, but the description fails to disclose critical behavioral traits: whether this requires specific permissions or authentication, if it's idempotent or destructive (e.g., overwrites existing configs), what happens on success or error, or any rate limits. For a mutation tool with zero annotation coverage, this leaves significant gaps in understanding how the tool behaves.

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—a single three-word sentence—with no wasted words. It's front-loaded with the core action ('Sets'), but this brevity comes at the cost of clarity and completeness. While efficient, it under-specifies rather than being optimally concise, as it omits necessary context that would help an agent use the tool effectively.

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 of a mutation tool with three required parameters, no annotations, and no output schema, the description is incomplete. It doesn't explain what transport configurations are, the system context (e.g., SAP or version control), expected outcomes, error conditions, or how it differs from sibling tools. For a tool that likely modifies critical system settings, this lack of detail is inadequate and could lead to misuse.

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%, with all three parameters (uri, etag, config) having clear descriptions in the schema. The tool description adds no additional meaning about parameters—it doesn't explain what a 'transport configuration' entails, how the URI relates to it, or what the ETag is used for (e.g., concurrency control). Since the schema does the heavy lifting, the baseline score of 3 is appropriate, but the description doesn't compensate with any extra insights.

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 'Sets transport configurations' is a tautology that essentially restates the tool name 'setTransportsConfig'. It lacks specificity about what transport configurations are, what system or resource they belong to, or what the action entails beyond the generic verb 'sets'. While it indicates a write operation, it doesn't distinguish this tool from potential siblings like 'createTransportsConfig' or 'getTransportConfiguration' beyond the basic verb difference.

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. It doesn't mention prerequisites (e.g., needing an existing transport configuration to modify), compare it to sibling tools like 'createTransportsConfig' (for initial creation) or 'getTransportConfiguration' (for reading), or specify scenarios where this tool is appropriate. Without any contextual cues, an agent would struggle to determine when this tool is the correct choice.

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