mcp-abap-adt

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 mentions the action is a 'List' operation, implying it's read-only, but doesn't specify whether it requires authentication, has rate limits, returns paginated results, or what format the output takes. The description is minimal and lacks important operational context.

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 that communicates the core purpose with an example. There's no wasted language or unnecessary elaboration, making it easy to parse quickly while still being informative.

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 tool with no annotations and no output schema, the description is insufficiently complete. It doesn't explain what the output looks like, whether it's a simple list or structured data, or any behavioral characteristics like error conditions or performance considerations. The single-sentence description leaves too many operational questions unanswered.

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 description provides no information about the single parameter 'response_format', which has 0% schema description coverage. However, since there's only one parameter with a clear enum (xml/json/plain) and a default value (xml), the schema itself provides adequate documentation. The description adds no value beyond what the schema already provides.

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 ('List') and resource ('available service binding types') with a specific example ('ODataV2/ODataV4') and source ('from ADT Business Services endpoint'). It distinguishes itself from sibling tools like GetServiceBinding or CreateServiceBinding by focusing on listing types rather than individual instances or creation 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?

The description provides no guidance on when to use this tool versus alternatives. While it mentions the source endpoint, it doesn't specify prerequisites, timing considerations, or compare it to similar tools like GetAdtTypes or GetServiceBinding that might retrieve related information.

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