GetBehaviorDefinitionVersionSource

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

The description includes a '[read-only]' tag upfront, which is a behavioral hint. It states it fetches source, but does not disclose potential errors, rate limits, or output format. Without annotations, the description provides basic but not comprehensive 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 a single, well-structured sentence front-loaded with the read-only indicator. Every part is useful and 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 low complexity (one parameter, no output schema, no annotations), the description adequately explains the input source and basic function. It could be improved by mentioning what the source output looks like (e.g., source code text) but is sufficient for a simple fetch operation.

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 with a description for content_uri. The tool description adds the context that the content_uri is from GetBehaviorDefinitionVersions, which is valuable beyond the schema's 'opaque' description.

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 fetches the source of a specific RAP behavior definition version using a content_uri. It distinguishes from sibling Get*VersionSource tools by specifying the object type (RAP behavior definition).

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 indicates that the content_uri comes from a GetBehaviorDefinitionVersions entry, providing clear context for usage. However, it does not explicitly state when not to use or mention alternative tools, though the sibling list contains many similar tools.

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