mcp-abap-adt

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

The description includes '[read-only]' which discloses a key behavioral trait (non-destructive operation). Since no annotations are provided, this adds important context. However, it doesn't mention other behavioral aspects like rate limits, authentication requirements, error conditions, or what format the metadata/implementations are returned in.

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 appropriately brief (one sentence) and front-loaded with the key information. The '[read-only]' prefix efficiently communicates an important behavioral trait. No unnecessary words or redundant information is present.

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 read-only tool with one well-documented parameter but no output schema, the description provides basic purpose and safety information. However, it lacks details about return format, error handling, or how the 'list of implementations' is structured, leaving gaps that could hinder effective tool use.

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 single parameter 'enhancement_spot' is fully described in the schema), the description adds no additional parameter information beyond what's already in the structured data. The baseline score of 3 reflects adequate but minimal value added regarding parameters.

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 tool's purpose with a specific verb ('Retrieve') and resource ('metadata and list of implementations for a specific enhancement spot'). It distinguishes from some siblings like 'GetEnhancements' (plural) by focusing on a single spot, but doesn't explicitly differentiate from all similar 'Get' tools in the list.

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 like 'GetEnhancements' or 'GetEnhancementImpl'. It states what it does but offers no context about prerequisites, when it's appropriate, or what distinguishes it from sibling tools.

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