UpdateBehaviorDefinition

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

Explains the locking, update, unlock, and optional activation process, which adds behavioral context beyond the schema. However, fails to mention error conditions or what happens on failure. No annotations provided, so description carries full burden.

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?

Three sentences; the first is somewhat redundant ('Operation: Update, Create. Subject: BehaviorDefinition.'). Could be more concise without losing meaning.

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?

Lacks explanation of return values, prerequisites (e.g., transport request importance), or error scenarios. Given no output schema or annotations, the description should provide more comprehensive context for this 5-parameter mutation tool.

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?

All 5 parameters are documented in the schema (100% coverage), so the description adds minimal semantic value. The mention of 'locks' hints at lock_handle usage but does not elaborate beyond the schema.

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 it updates source code of an existing Behavior Definition, specifying the verb and resource. However, the mention of 'Create' in the first sentence creates potential confusion with the sibling tool CreateBehaviorDefinition.

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 on when to use this tool versus alternatives like CreateBehaviorDefinition or CheckBehaviorDefinition. The description only vaguely says 'will be useful' without explicit context or exclusions.

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