wave_create_account

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

The description only states the action. No behavioral traits beyond creation are disclosed. For a write operation with no annotations, it should mention side effects, auth requirements, or constraints (e.g., uniqueness of account name).

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?

Single sentence that is concise and front-loaded. Every word is necessary and informative.

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?

Adequate for a simple creation tool with a comprehensive schema. However, the lack of output schema and annotations means the description could be more complete by explaining the return value or confirmation behavior.

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 100%, so baseline is 3. The description does not add any parameter-specific meaning beyond the schema. It does not explain the relationship between parameters or provide format hints.

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 creates a new account in the chart of accounts. It uses a specific verb ('Create') and resource ('account in the chart of accounts'), and is distinct from siblings like wave_list_accounts and wave_update_account.

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?

No explicit guidance on when to use this tool versus alternatives. The verb 'Create' implies it is for new accounts, but prerequisites (e.g., need a business ID) or scenarios for updating vs. creating are not mentioned.

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