bw_update_adso

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

Discloses that the operation returns a lock_handle and requires a sequence of activations. Mentions removal of key fields for remove_field. Lacks details on prerequisites (e.g., aDSO state), reversibility, and side effects like data impact. No annotations, 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?

Description is dense but well-organized by actions. Each sentence adds value. Could benefit from bullet points for readability, but is appropriately sized and front-loads the main purpose.

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?

Explains all actions and return value (lock_handle). Covers the activation sequence. Missing details on error handling, defaults, and consequences of not using the lock_handle. For a tool with high complexity and no output schema, it is mostly 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 description coverage is 100%, so baseline is 3. The tool description adds value by explaining parameter relationships per action (e.g., infoobject_name required for add_field/remove_field), but does not significantly expand beyond schema descriptions.

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 explicitly states it updates aDSO with multiple actions (add_field, remove_field, add_pure_field, update_settings, manage_keys, update_field_properties), clearly distinguishing from sibling tools like bw_create_adso which creates aDSOs.

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?

Provides clear context on when to use each action and the required parameters for each. Describes the necessary activation sequence (bw_update_adso → bw_activate). However, does not explicitly list alternatives or when not to use this tool.

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