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

Annotations already indicate destructiveHint: true and readOnlyHint: false, signaling this is a write operation with potential destructive effects. The description adds little beyond stating the action; it does not explain what happens to the position after removal, whether the operation is reversible, or any specific authorization requirements. The SAP MCP context covers execution details but not behavioral side effects.

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 contains a concise first sentence, but the second sentence is a long, generic paragraph about SAP MCP workflow that is not specific to this tool. This padding detracts from readability and focus. The tool definition could be significantly shortened by moving the generic SAP context elsewhere.

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?

Even though an output schema exists (and annotations provide some hints), the description does not explain the outcome of removing collateral, such as whether the position remains open or if funds are returned. For a destructive mutation tool, more context about side effects and safety considerations is needed to help the agent use it correctly.

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% coverage with clear descriptions for all three parameters (amount, wallet, positionKey). The description does not add any additional meaning or constraints beyond the schema. The baseline is appropriate here since the schema already handles parameter documentation adequately.

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 'Remove collateral from an Adrena position', which is a specific verb+resource combination. This distinguishes it from sibling tools like adrena_addCollateral and adrena_closePosition. However, the purpose is somewhat buried under extensive SAP MCP context that is not directly about the tool's core action.

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 does not provide any guidance on when to use this tool versus alternatives, nor does it mention prerequisites or scenarios where the tool should be avoided. The SAP MCP context discusses pricing and routing but is generic and does not help an agent decide when to invoke this specific tool.

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