GetBehaviorDefinitionVersionDiff

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

The description includes '[read-only]' indicating non-destructive behavior, but with no annotations, it does not disclose other traits like output format, error handling, or performance implications, leaving gaps for an agent.

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 concise sentence, front-loaded with '[read-only]', and every part provides essential information without redundancy.

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?

Missing an output schema, the description does not specify the format or structure of the unified diff result. While it hints at a unified diff, it lacks details on what the agent can expect as output, which is needed for full completeness.

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 parameter descriptions. The description adds value by clarifying that content_uris are derived from GetBehaviorDefinitionVersions entries, enhancing context 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 explicitly states it computes a unified diff between two RAP behavior definition versions using content_uris from GetBehaviorDefinitionVersions, clearly distinguishing it from other version diff tools for different object types.

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?

It specifies that content_uris should be taken from GetBehaviorDefinitionVersions entries, providing input provenance. However, it lacks explicit guidance on when to use this tool versus alternative diff tools or contexts where it should not be used.

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