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, but it only states the action without details on permissions, rate limits, side effects, or return format. 'Accesses' is ambiguous—it could imply read-only or mutation behavior, but this is not clarified, leaving the agent with insufficient information to understand the tool's behavior.

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, straightforward sentence with no wasted words, making it appropriately concise. However, it lacks front-loaded critical information (e.g., purpose differentiation or behavioral context), which slightly reduces its effectiveness despite the brevity.

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 lack of annotations and output schema, the description is incomplete for a tool with one parameter. It fails to explain what 'accesses' entails, the expected return values, or how it interacts with the DDIC repository, leaving significant gaps in understanding for an AI agent.

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 'path' parameter documented as 'The path to the DDIC element.' The description does not add any meaning beyond this, such as format examples or constraints, but since schema coverage is high, a baseline score of 3 is appropriate as the schema carries the burden.

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 'Accesses the DDIC repository' restates the tool name 'ddicRepositoryAccess' with minimal elaboration, making it tautological. It specifies the resource (DDIC repository) but lacks a clear, specific verb beyond 'accesses', which is vague compared to sibling tools like 'ddicElement' or 'checkRepo' that suggest more concrete actions.

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 any context, prerequisites, or exclusions, and with many sibling tools (e.g., 'ddicElement', 'findDefinition'), there is no indication of how this tool differs or when it should be selected.

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