billy_update_account

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

With no annotations, the description bears full burden. It discloses the mutation nature and confirm requirement, but lacks details on error handling, idempotency, or what fields are updatable. The patch object being free-form is not mentioned.

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 very short (two sentences) but misses critical information about parameters and behavior. It is under-informative, not efficiently concise.

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 tool has a two-phase commit pattern (dry-run vs execute) and no output schema, the description does not explain the dry-run preview or define what 'id' and 'patch' represent. It is incomplete.

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 only 33% (only confirm has a description). The tool description does not add meaning for 'id' or 'patch' parameters. The confirm behavior is explained in the schema, but the overall parameter semantics are insufficiently described.

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 'Update an existing account', which is a specific verb and resource. It distinguishes from create tools, though it does not explicitly differentiate from other update-type siblings.

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 includes 'WRITE — requires confirm:true' which provides usage context about the confirmation mechanism. However, it does not offer guidance on when to use this tool versus alternatives like billy_create_account or other update tools.

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