mcp-abap-adt

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

No annotations are provided, so the description carries full burden. While 'Delete' implies a destructive operation, the description doesn't disclose critical behavioral traits: whether deletion is permanent/reversible, what permissions are required, whether it affects dependent objects, or what happens if the binding doesn't exist. The ADT endpoint mention adds some context but insufficient 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's appropriately sized for a tool with clear purpose and front-loaded with the essential action and target. Every word earns its place.

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 destructive mutation tool with no annotations and no output schema, the description is inadequate. It doesn't explain what happens after deletion, what errors might occur, or what the response contains. With 67% schema coverage and one parameter having only a default/enum without semantic explanation, significant gaps remain for proper tool invocation.

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 67% (2 of 3 parameters have descriptions). The description adds no parameter information beyond what's in the schema. With moderate schema coverage, the baseline is 3 - the description doesn't compensate for the undocumented 'response_format' parameter but also doesn't contradict the schema.

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 clearly states the action ('Delete') and target resource ('ABAP service binding'), and specifies the mechanism ('via ADT Business Services endpoint'). It distinguishes from sibling tools like 'CreateServiceBinding' and 'UpdateServiceBinding' by focusing on deletion, but doesn't explicitly contrast with other delete operations like 'DeleteServiceDefinition'.

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 doesn't mention prerequisites, when deletion is appropriate, or what happens after deletion. With many sibling tools including other delete operations, this lack of context leaves the agent guessing about appropriate usage scenarios.

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