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. The description only states 'Accesses the DDIC repository' without explaining what this access entails - whether it's read-only or mutative, what permissions are required, what happens when invoked, or what kind of response to expect. For a tool with no annotation coverage, this is completely inadequate behavioral transparency.

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 just three words. While this represents under-specification rather than ideal conciseness, within the conciseness dimension, it earns maximum points for having zero wasted words and being front-loaded with the core statement. Every word in 'Accesses the DDIC repository' directly contributes to the description.

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 has no annotations, no output schema, and a vague description, the contextual completeness is severely lacking. For a tool that presumably interacts with a critical system component (DDIC repository), the description fails to provide necessary context about what the tool does, how it behaves, what it returns, or when to use it. The agent would struggle to understand this tool's role among 100+ sibling tools.

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 schema description coverage is 100% (the 'path' parameter is fully documented in the schema), so the baseline score is 3. The description adds no additional parameter information beyond what's already in the schema. It doesn't explain what constitutes a valid DDIC path, provide examples, or clarify the parameter's role in the access operation.

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' is a tautology that essentially restates the tool name 'ddicRepositoryAccess'. It provides a vague purpose without specifying what type of access (read, write, query, etc.) or what resource within the repository is being accessed. While it mentions the DDIC repository, it doesn't distinguish this tool from other repository-related tools like 'ddicElement' or 'checkRepo'.

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. There is no mention of prerequisites, context, or comparison to sibling tools like 'ddicElement' or 'checkRepo'. The agent receives no information about appropriate use cases or when this tool would be preferred over other repository access methods.

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