bolna_update_disposition

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

The description discloses the copy-on-write behavior when scoped to an agent, which is a key behavioral trait. However, with no annotations, it fails to mention other important aspects like permissions, idempotency, or error handling.

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 extremely concise at one sentence, which is a strength. However, it could be slightly more structured to separate the main action from the behavioral note.

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 complexity (11 parameters, no output schema, no annotations), the description is incomplete. It does not explain update semantics (partial vs full), return values, or error conditions, leaving significant gaps for the agent.

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 only 18%, and the tool description adds no additional parameter semantics beyond what is already in the schema. The remaining 9 parameters are left undocumented, forcing the agent to rely on naming conventions.

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 action ('update a disposition') and the resource, which distinguishes it from create or delete tools. However, it does not elaborate on what aspects can be updated beyond the schema fields.

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 does not explicitly state when to use this tool versus alternatives like create or delete. The context is implied but lacks explicit guidance on prerequisites or exclusions.

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