ABAP-ADT-API MCP-Server

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

With no annotations provided, the description carries the full burden of behavioral disclosure but offers none. It does not indicate whether this is a read or write operation, what permissions are required, if it's idempotent, or what the expected outcome is. For a tool named 'request', which implies a mutation, this lack of transparency is critical.

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 at three words, with no wasted verbiage. It is front-loaded with the core action, though this brevity comes at the cost of clarity and completeness. Every word serves a purpose, even if insufficient.

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?

For a tool with no annotations, no output schema, and a single but nested parameter, the description is incomplete. It fails to explain the tool's behavior, expected inputs beyond the schema, or what the request entails. Given the complexity implied by 'ATC exemption' and the lack of structured data, more context is needed.

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 input schema has 100% description coverage, with the single parameter 'proposal' described as 'The ATC exemption proposal'. The description adds no additional meaning beyond this, as it does not elaborate on what constitutes a proposal or its structure. Given the high schema coverage, the baseline score of 3 is appropriate.

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 'Requests an ATC exemption' restates the tool name 'atcRequestExemption' almost verbatim, making it tautological. It lacks specificity about what an ATC exemption entails or what resource it acts upon, beyond the generic verb 'requests'. Compared to sibling tools like 'atcExemptProposal' or 'atcChangeContact', it fails to distinguish its unique function.

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 guidance is provided on when to use this tool versus alternatives. The description does not mention prerequisites, context, or exclusions, nor does it reference sibling tools like 'atcExemptProposal' or 'atcCustomizing' that might be related. This leaves the agent with no usage context.

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