CreateBehaviorDefinition

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

With no annotations provided, the description must fully disclose behavioral traits. It only states 'Create' without detailing side effects (e.g., activation, transport handling, overwrite behavior). The schema includes an 'activate' parameter but the description doesn't mention default activation or consequences of creation.

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 two sentences and to the point, with no redundancy. It could be slightly more streamlined, but it's effective in conveying the core 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?

Given the complexity (7 parameters, 4 required, no output schema, no annotations), the description lacks context about the creation process, expected outcomes, or how this tool fits into the larger RAP development workflow. Sibling tools are numerous, and more specific context would help.

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 baseline is 3. The description adds no parameter-specific information beyond what the schema already provides; it only gives a high-level overview of the BDEF's purpose, which is not directly about 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 action ('Create') and resource ('ABAP Behavior Definition (BDEF)'), and explains what a BDEF defines (RAP business object behavior: CRUD operations, etc.). This clearly distinguishes it from sibling tools like UpdateBehaviorDefinition or CreateBehaviorImplementation.

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 provide any guidance on when to use this tool versus alternatives (e.g., should the user create a BDEF before creating implementation?), nor does it mention prerequisites like needing an existing CDS view or package. The 'when to use' context is absent.

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