billy_create_account

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

The description discloses that it is a WRITE operation and requires confirm:true, which is important behavioral context. However, no annotations are provided, and the description lacks details on side effects (e.g., idempotency, behavior on duplicate accounts) and outcome beyond the dry-run mechanism explained in the schema.

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 with one sentence, front-loading the purpose. However, it sacrifices completeness for brevity; slightly more structure (e.g., separate lines for parameter hints) would improve usability.

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 (nested account object, write operation with dry-run, no output schema), the description is insufficient. It does not explain what the account object should contain, nor does it describe the return value or error conditions, leaving the agent under-informed.

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 50% (confirm described, account not). The description does not add any parameter information beyond the schema, leaving the account object's structure undocumented. With a nested object, this is a significant gap that the description fails to address.

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 'Create a new account in the chart of accounts', which specifies the verb (create) and unique resource (account in chart of accounts), distinguishing it from siblings like billy_list_accounts (read) and billy_update_account (update).

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 is a key usage condition but does not provide explicit guidance on when to use this tool versus alternatives (e.g., billy_update_account for modifications). No when-not-to-use or alternative suggestions are given.

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