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. 'Sets trace parameters' implies a mutation/write operation but provides no information about permissions required, whether changes are reversible, side effects, rate limits, or what happens after parameters are set. This is inadequate for a mutation tool with zero annotation coverage.

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 maximally concise at just three words. There's zero wasted language or unnecessary elaboration. While this conciseness comes at the expense of completeness, as a standalone attribute, the description is perfectly structured and front-loaded.

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 completely inadequate. It doesn't explain what trace parameters are, what values they accept, what the tool actually does with them, or what happens after setting them. Given the complexity implied by having sibling tools for trace configuration management, this minimal description fails to provide necessary context.

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 already documents the single 'parameters' parameter as 'The trace parameters.' The description adds no additional meaning beyond what the schema provides - it doesn't explain parameter format, syntax, examples, or constraints. The baseline of 3 is appropriate when the schema does the documentation work.

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 'Sets trace parameters' is a tautology that essentially restates the tool name 'tracesSetParameters'. It specifies the verb ('Sets') and resource ('trace parameters'), but provides no additional detail about what trace parameters are or what specific operation occurs. It doesn't distinguish this from sibling trace tools like tracesCreateConfiguration or tracesDeleteConfiguration.

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 absolutely no guidance about when to use this tool versus alternatives. There are multiple sibling trace tools (tracesCreateConfiguration, tracesDeleteConfiguration, tracesList, tracesHitList, etc.), but the description offers no context about when this specific parameter-setting tool is appropriate versus those other trace operations.

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