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 must fully disclose behavioral traits. It only states 'Retrieves... information', which implies a read-only operation but doesn't clarify permissions, rate limits, side effects, or response format. This leaves critical behavioral aspects undocumented.

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, efficient sentence with no wasted words. It is appropriately sized and front-loaded, though this conciseness comes at the cost of completeness.

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 tool with 4 undocumented parameters, no annotations, and no output schema, the description is completely inadequate. It doesn't explain what the tool returns, how parameters interact, or any behavioral context, leaving the agent with insufficient information to use the tool 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?

The input schema has 4 required parameters with 0% description coverage, meaning none are documented in the schema. The description adds no information about what 'sourceUrl', 'source', 'line', or 'column' mean or how they should be used, failing to compensate for the schema's lack of documentation.

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 'Retrieves code completion element information' restates the tool name 'codeCompletionElement' in a slightly different phrasing, making it tautological. It doesn't specify what kind of information is retrieved or how it differs from sibling tools like 'codeCompletion' or 'codeCompletionFull', leaving the purpose vague.

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?

There is no guidance on when to use this tool versus alternatives such as 'codeCompletion' or 'codeCompletionFull'. The description provides no context, prerequisites, or exclusions, making it impossible for an agent to determine appropriate usage scenarios.

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