CreateMetadataExtension

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

No annotations are provided, so the description carries full burden for behavioral disclosure. It only states creation and general purpose but does not mention required authorizations, side effects, or whether existing extensions are overwritten. The 'activate' parameter implies an activation step, but without explanation of its implications, the description is insufficiently transparent 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 extremely concise—two sentences, no wasted words. It front-loads the core action and domain, making it easy for an AI agent to quickly grasp the tool's purpose.

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?

The description provides the essential purpose but lacks details on prerequisites (e.g., existence of a CDS view), what happens if activation fails, or the results of creation. Given that there is no output schema and the tool creates a resource with potential dependencies, a more complete description would include such context. However, it is minimally adequate for a straightforward creation tool.

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 coverage is 100%, providing a baseline of 3. The description adds meaningful context by explaining that the metadata extension defines 'Fiori UI annotations, field labels, search help, and list/object page layout for CDS views,' which enhances understanding of the parameters' roles (e.g., 'description' likely refers to the extension's description). This goes beyond merely restating parameter names.

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 it creates an ABAP Metadata Extension (DDLX) and specifies its purpose: defining Fiori UI annotations, field labels, search help, and layout for CDS views. This is a specific verb+resource pair that distinguishes it from sibling tools like CreateBehaviorDefinition or CreateServiceDefinition.

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 explicit guidance on when to use this tool versus alternatives, nor does it mention when not to use it or any prerequisites. The absence of comparative context leaves the AI agent without clear decision-making support beyond the inferred domain (Fiori annotations for CDS views).

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