GetBehaviorDefinition

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

With no annotations present, the description must disclose behavioral traits. It implicitly indicates a read-only operation by using 'Retrieve', but it does not explicitly state that it is non-destructive or whether any locking occurs. The version parameter behavior is already clear from the schema, so the description adds minimal new context.

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 very concise with only two sentences. However, it contains a minor redundancy ('definition definition') and could be slightly more polished. Despite this, it is appropriately front-loaded and free of extraneous content.

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, the description should explain what the tool returns, such as whether it provides the definition source code or metadata. It does not, leaving the agent without crucial information about the result. The context signals indicate no output schema, so the description's omission is a significant gap.

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 already provides complete descriptions for both parameters with 100% coverage. The description redundantly mentions the version parameter but adds no additional meaning beyond what the schema offers. Thus, it meets the baseline without extra value.

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 verb 'Retrieve' and the resource 'ABAP behavior definition definition', which effectively distinguishes it from sibling tools that retrieve other objects (e.g., GetClass, GetDataElement). The mention of supporting active or inactive versions further clarifies the tool's specific capability.

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 provides no guidance on when to use this tool versus alternatives. There is no mention of prerequisites, typical scenarios, or comparisons to siblings like CheckBehaviorDefinition or GetObjectInfo. An agent would need to infer usage from the name alone.

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