Create Wave product or service

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

Annotations already declare this is a non-readonly, open-world, non-idempotent creation operation. The description adds the critical constraint that income_account_id must be an INCOME, DISCOUNTS, or OTHER_INCOME account, which is valuable validation context beyond the schema. It does not cover permissions, side effects, or error conditions.

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?

Three tight sentences, each earning its place: purpose, pre-check, and a critical parameter constraint. Front-loaded and waste-free.

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 mutation annotations, an output schema, and 60% schema coverage, the description equips an agent to call the tool correctly. It could mention the pre-check's purpose more explicitly or note that unit_price format is schema-documented, but it is largely complete.

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 60%, so the description compensates by clarifying the subtype constraint on income_account_id, which the schema only calls an 'opaque string'. This is meaningful added semantics, though it could say more about default_sales_tax_ids and name.

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?

States a specific verb (Create) and resource (product/service usable on invoice line items), which distinguishes it from siblings like wave_create_invoice and wave_create_customer. The purpose is immediately clear.

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?

Explicitly instructs to check wave_list_products first, which is a concrete usage guideline. However, it does not state when not to create or describe alternative approaches, so it falls short of a 5.

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