CreateDdl

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

No annotations are provided, so the description must carry the transparency burden. It discloses that the tool creates the object in an initial state, implying no code is set. However, it does not mention that a transport request may be required for transportable packages or what happens if the object already exists. This is a moderate gap.

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 four sentences. It front-loads the key action ('Operation: Create. Subject: DDL source.') and then provides the necessary context. Every sentence is meaningful and no redundant information.

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?

Given the number of parameters (5) and the absence of an output schema, the description adequately covers the main purpose and key distinction from siblings. It mentions that the object is created in initial state and points to UpdateDdl for setting code. Minor missing details like conditional transport request requirement, but overall complete for typical agent 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?

The schema has 100% description coverage, so baseline is 3. The description does not add any additional meaning or context for the parameters beyond what is already in the schema. It does not elaborate on any parameter, so no extra value is provided.

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 explicitly states it creates a new CDS View or Classic View in SAP system, creating the DDL source object in initial state. It distinguishes from UpdateDdl by mentioning that UpdateDdl sets the source code, so the purpose is clear and distinct from siblings.

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 a clear guideline: 'Use UpdateDdl to set DDL source code.' This tells the agent when to use this tool vs. the alternative. However, it does not explicitly state when not to use it or other conditions, but the context is sufficient for typical usage.

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