Wave: Set Default Business

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

Adds substantial behavior beyond annotations: the default is connector state, is scoped per authenticated connection or local server lifetime, becomes permanent with WAVE_BUSINESS_ID, and is always overridden by explicit business_id. This is rich context for a state-setting tool whose annotations already indicate non-read-only, idempotent, non-destructive behavior.

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 front-loaded with the core action, then efficiently covers state semantics, persistence, and override behavior in four short sentences. No sentence is filler.

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 one-parameter connector-state tool with no output schema, the description covers purpose, scope, persistence, and override behavior completely. An agent has what it needs to call it correctly.

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% and already documents the business_id format (base64 ID or bare UUID). The description adds useful parameter interaction semantics by stating that passing business_id explicitly always overrides the default being set.

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 the specific action ('Set the business that later tool calls use when none is given') and clarifies it is connector state rather than a Wave data change. This distinguishes it clearly from sibling read/list tools like wave_get_business and wave_list_businesses.

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?

Explains when the setting applies ('later tool calls use when none is given') and notes that explicit business_id overrides it. It does not explicitly state when not to use it, but the relevant context and alternative override behavior are clear.

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