update_bot

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

Annotations indicate destructive and not read-only; the description adds crucial behavioral details beyond annotations, such as the silent ignoring of feature value fields when their toggle is false. This transparency helps the agent avoid unexpected behavior.

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 three clear, efficient sentences with no wasted words. The most important information (purpose and constraints) is front-loaded.

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?

For a simple update tool with full schema coverage and annotations, the description covers purpose, usage, constraints, and a behavioral quirk. Missing a note about the return value, which could be inferred but not stated.

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 the description adds little to parameter understanding beyond what the schema provides. The description re-emphasizes the partial update strategy but does not introduce new parameter semantics.

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 updates existing bots, specifying DCA or Combo only, directly distinguishing it from create_bot and other siblings. The verb-resource pairing is precise.

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 explicit guidance on partial updates ('Pass only the fields you want to change'), a constraint on the settings object (must be non-empty), and a behavioral note about boolean gates. It also clarifies that Grid bots are not supported, helping the agent avoid calling the tool incorrectly.

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