GetBehaviorDefinition

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

With no annotations, the description carries the full burden. It implies a read-only retrieval and discloses that both active and inactive versions can be read, which is useful context. However, it says nothing about permissions, behavior when the object does not exist, or whether inactive reads require special state — gaps that matter for an unannotated 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?

Two short sentences with the primary purpose front-loaded and no filler. The duplicated 'definition definition' is the only rough edge.

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?

For a simple two-parameter getter with no output schema and full schema coverage, the description supplies enough to call the tool correctly. Minor missing pieces (error/no-found behavior) are acceptable given the tool's simplicity.

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% and both parameters are fully documented, including the active/inactive enum and default. The description's version sentence merely restates what the schema already says, adding no syntax or semantic value beyond it.

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?

States a specific verb (Retrieve) and resource (ABAP behavior definition), clearly distinguishable from siblings such as GetBehaviorImplementation or GetBehaviorDefinitionVersionSource. The phrasing 'behavior definition definition' is redundant but does not impair comprehension.

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 second sentence implies the tool is used when either the active or inactive version is needed, but there is no explicit when-to-use guidance, no mention of when to prefer GetBehaviorDefinitionVersionSource or GetBehaviorDefinitionVersions, and no prerequisites.

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