UpdateDdl

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

With no annotations, the description discloses the lock-update-unlock-activate sequence, providing useful behavioral context. However, it omits details on failure states, idempotency, or side effects.

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 has redundancy (e.g., repeating 'Update, Create' and 'DDL source') and could be more streamlined. It is not excessively long but could be tighter.

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 complexity of updating ABAP DDL sources, the description covers the main actions but lacks return value info and error handling details. It is adequate but not thorough.

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% and the description adds little beyond the schema's parameter descriptions. The mention of locking/activation provides some context but no additional semantic detail.

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 updates DDL source code of an existing CDS or Classic View, distinguishing it from CreateDdl for new sources. The verb and resource are precise.

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 differentiates from CreateDdl but lacks explicit guidance on when to use vs other siblings like ActivateDdl or CheckDdl. It mentions the optional activation and transport requirement, but could be more directive.

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