GetBehaviorDefinitionVersions

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

No annotations provided, so description carries full burden. It declares the tool as '[read-only]', which is critical behavior. It lists all return fields including the opaque content_uri and references a related tool for fetching source. Does not cover auth or rate limits, but for a read operation this is sufficient.

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?

Single sentence packs key info: read-only flag, purpose, returned fields. Efficient but could benefit from splitting into multiple lines for readability. No redundant words.

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?

No output schema provided, but description lists all returned fields. Covers purpose, parameter, and outcome. References a sibling tool for further action (fetching source). For a list operation, this is fairly complete.

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 coverage is 100% with a single parameter described as 'RAP behavior definition name.' The description adds no new information beyond the schema, so baseline score of 3 applies.

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?

Description clearly states 'list the SAP version history of a RAP behavior definition' with specific verb+resource. Distinguishes from sibling version tools by specifying 'RAP behavior definition', making it unique among many Get...Versions tools.

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 explicit guidance on when to use vs alternatives. The description implies usage for listing versions of a behavior definition, but does not mention when not to use or point to sibling tools like GetBehaviorDefinitionVersionDiff for comparison purposes.

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