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 action ('pulls changes') but doesn't cover critical aspects like authentication needs (implied by user/password params), potential side effects (e.g., merging changes), error conditions, or response format. This leaves significant gaps for a mutation tool.

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 zero wasted words. It is front-loaded and directly states the tool's purpose without unnecessary elaboration, making it easy to parse quickly.

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's complexity (Git operation with 5 parameters, no output schema, and no annotations), the description is inadequate. It doesn't explain what 'pulls changes' entails operationally, authentication requirements, or expected outcomes, leaving the agent with insufficient context for reliable 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?

Schema description coverage is 100%, so the schema fully documents all parameters (repoId, branch, transport, user, password). The description adds no additional meaning beyond the schema, such as explaining parameter interactions or default behaviors, but meets the baseline for high schema coverage.

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 'Pulls changes from a Git repository' clearly states the action (pull) and resource (Git repository), making the purpose evident. It distinguishes from sibling tools like 'gitCreateRepo' or 'pushRepo' by focusing on pulling changes, but it doesn't specify scope or constraints beyond the basic verb.

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 lacks context about prerequisites (e.g., repository setup), exclusions, or comparisons to other Git-related tools like 'pushRepo' or 'stageRepo', leaving the agent without usage direction.

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