GetMetadataExtension

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

No annotations are provided, so the description carries full burden. It states the tool retrieves definitions and supports version selection, implying a read operation. However, it does not explicitly declare read-only nature, lack of side effects, or any other behavioral traits beyond what is in the schema.

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 very concise with two sentences, each earning its place. It is front-loaded with the main action. However, it lacks structure or additional details that could aid comprehension, but the brevity is appropriate for a simple tool.

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?

With no output schema, the description should explain the return value or shape. It does not. Given the tool's simplicity (2 params), the description is partially complete but fails to inform agents about what the retrieved definition contains. This gap reduces completeness.

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 both parameters. The description adds no additional meaning or examples beyond what is in the schema. Baseline score of 3 applies as the description does not enhance parameter understanding.

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 retrieves an 'ABAP metadata extension definition' with explicit verb 'Retrieve' and resource. It distinguishes from siblings by specifying version support (active/inactive), which aligns with the tool's name and differentiates it from update/create/delete tools.

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 explicitly state when to use this tool versus alternatives (e.g., other Get* tools or metadata extension tools). The version feature is mentioned, but no guidance on when to choose active vs inactive or when to use different retrieval tools. The purpose is implied but not explicitly contrasted.

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