Create account

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

The description is consistent with the annotations: 'Add' aligns with readOnlyHint=false and destructiveHint=false. It adds the useful behavioral detail that subtype determines account type, but it does not elaborate on permissions, validation, duplicate handling, or other mutation consequences beyond what the annotations already say.

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?

Two short sentences with no filler, front-loaded with the action and followed by the key subtype dependency. Nothing is wasted.

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?

For a six-parameter create tool with no output schema, the definition covers the core action and the most important subtype relationship. It remains thin on mutation behavior, return expectations, duplicate constraints, and business-context requirements, leaving meaningful gaps for an agent invoking it.

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 50%, so the description should compensate more than it does. It adds meaningful semantics for subtype by explaining that it decides the account type and pointing to wave_get_reference, but it says nothing about name, description, duplicate naming, or the other optional parameters beyond what the schema already provides.

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 states a specific verb and resource: 'Add an account to the chart of accounts.' That distinguishes creation from sibling tools such as wave_update_account and wave_archive_account, though it does not explicitly name those alternatives.

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?

Usage is implied by 'Add an account', and the pointer to wave_get_reference for subtype selection gives practical setup guidance. However, it does not say when to create versus update, archive, or list accounts, nor does it state prerequisites or exclusions.

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