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. It states the tool 'retrieves information,' implying a read-only operation, but does not specify what information is returned, whether authentication is required, or any rate limits or errors. For a tool with no annotations, this leaves critical behavioral traits undocumented, though it does not contradict any annotations.

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 that efficiently conveys the core purpose without unnecessary details. It is front-loaded and wastes no words, making it easy to parse. However, it could be slightly more informative without sacrificing conciseness, such as by hinting at the type of information retrieved.

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 Git repository tool with no annotations and no output schema, the description is insufficient. It does not explain what information is retrieved (e.g., metadata, branches, commits), potential authentication needs, or error handling. For a tool that likely returns structured data, the lack of output details or behavioral context makes it incomplete for effective agent use.

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 clear documentation for 'repourl,' 'user,' and 'password.' The description does not add any meaning beyond the schema, such as explaining parameter interactions or usage examples. Given the high schema coverage, the baseline score of 3 is appropriate, as the schema adequately handles parameter semantics without extra description.

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 states the tool 'retrieves information about an external Git repository,' which clearly indicates a read operation on a specific resource type. However, it does not differentiate this tool from sibling tools like 'gitRepos' or 'remoteRepoInfo,' leaving ambiguity about their distinct purposes. The description is functional but lacks specificity in scope or output compared to similar tools.

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 are sibling tools such as 'gitRepos' and 'remoteRepoInfo' that might overlap in functionality, but the description does not mention them or clarify contexts like external vs. internal repositories. This absence of comparative or contextual advice limits effective tool selection.

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