CreateBehaviorImplementation

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

With no annotations provided, the description bears the burden of behavioral disclosure. It states the object is created in 'initial state', indicating a non-destructive creation. However, it does not elaborate on error conditions, authorization needs, or whether the creation is immediately effective. The guidance to use UpdateBehaviorImplementation afterward adds context, but more detail on side effects would improve transparency.

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 unnecessary words. The first sentence states the purpose, the second gives usage guidance. Every word adds value, making it easy to parse.

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 the tool (creation with multiple parameters and no output schema), the description covers the essential flow: create then update. It does not mention return values or activation, but the flow is logical and the tool is part of a clear sequence with sibling tools. A slightly more detailed note on what the tool returns would push it to 5.

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 for all 5 parameters, so the tool description does not need to add parameter details. The description itself provides no additional parameter semantics, and according to the guidelines, a baseline of 3 is appropriate when schema coverage is high.

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 specifies the action: creating a new ABAP behavior implementation class for a behavior definition. The mention of 'initial state' and the sibling 'UpdateBehaviorImplementation' differentiates it from other creation tools like CreateClass and the update variant.

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 explicitly directs the agent to use UpdateBehaviorImplementation for setting implementation code after creation, providing a clear usage flow. It implies that the tool is only for the creation step and not for setting code, effectively guiding when to use it versus alternatives.

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