ABAP-ADT-API MCP-Server

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description carries full burden for behavioral disclosure. It states the action is 'activate' but doesn't explain what activation does (e.g., compile, make available for runtime), whether it's reversible, what permissions are required, or what side effects might occur. The description lacks critical behavioral context for a mutation operation.

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 6 words, which is efficient. However, this brevity comes at the cost of completeness - it's arguably too terse for a tool that performs a potentially significant system operation.

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?

For a mutation tool with no annotations and no output schema, the description is inadequate. It doesn't explain what 'activation' means operationally, what happens after activation, potential errors, or return values. Given the complexity implied by the parameter structure, more context is needed.

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?

With 100% schema description coverage, the schema already documents both parameters thoroughly. The description adds no additional parameter semantics beyond what's in the schema - it doesn't clarify the JSON array format further or explain the practical implications of the preaudit option.

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 'Activate ABAP objects using object references' states the action (activate) and target (ABAP objects), but is vague about what 'activate' means in this context. It doesn't differentiate from sibling tools like 'activateByName' or explain what activation entails compared to similar operations.

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 about when to use this tool versus alternatives like 'activateByName' or other object manipulation tools. The description offers no context about prerequisites, typical use cases, or when this specific activation method is appropriate.

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