GetBehaviorImplementation

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

With no annotations, the description must bear full responsibility for behavioral disclosure. It mentions version support but omits other critical traits such as read-only nature, required authorizations, or potential side effects. The description is insufficiently transparent.

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 a single sentence that directly conveys the tool's purpose and key capability (version support). Every word earns its place; there is no unnecessary 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 absence of an output schema and annotations, the description is too brief. It does not explain the return structure, any prerequisites, or how the version parameter affects results. For a retrieval tool among many similar siblings, more completeness is needed.

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 input schema has 100% coverage, so the description adds no new meaning beyond the parameter descriptions. The mention of version support aligns with the existing enum, but does not enhance semantic understanding. Baseline of 3 is appropriate.

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 retrieves an ABAP behavior implementation definition and supports active or inactive versions. This directly expresses the verb (Retrieve) and resource (behavior implementation definition), distinguishing it from sibling tools that create, update, or delete behavior implementations.

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?

No guidance is provided on when to use this tool over alternatives like GetBehaviorDefinition or other retrieval tools. There are no when-not scenarios or explicit comparisons with siblings, leaving the agent without decision criteria.

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