billy_create_bank_account

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

No annotations are provided, so the description carries the full burden. It states this is a WRITE operation requiring confirmation, which is transparent. However, it doesn't disclose side effects, authentication needs, or error behaviors. The input schema's confirm parameter adds detail, but the description itself is minimal.

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 a single sentence, front-loaded with the core action and the important WRITE/confirm constraint. No unnecessary words, but could be slightly expanded for completeness.

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?

The tool has a nested object parameter (bankAccount) and no output schema. The description does not explain return values, error conditions, or what constitutes a valid bankAccount object. The agent lacks sufficient context to use this tool correctly without additional knowledge.

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 50% (only confirm parameter has a description). The description adds no meaning beyond what the schema provides. It does not describe the bankAccount object structure, leaving the agent without guidance on required fields.

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 name 'billy_create_bank_account' clearly indicates a bank account creation. The description specifies 'Create a bank account in Billy' and adds the WRITE label, distinguishing it from siblings like 'billy_create_account' (general account) and other non-write tools.

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 explicitly states 'requires confirm:true', alerting the agent that a second call with confirm:true is needed to execute. While it doesn't compare to alternatives, this is a clear usage constraint.

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