Wave: Set Default Business

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

Annotations already declare idempotentHint=true and destructiveHint=false, so safety profile is covered. The description adds valuable context: this is connector state not a Wave change, with precise persistence semantics (session vs local server until restart, WAVE_BUSINESS_ID for permanent). This enriches the annotation profile without contradicting it.

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 with zero filler. The purpose is front-loaded, followed by state semantics and override note. Every sentence earns its place and the structure leads with the most actionable information.

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 single-parameter state setter with no output schema and informative annotations, the description covers purpose, persistence scope, override behavior, and side-effect-free nature. Nothing an agent needs to call it correctly is missing.

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 the parameter description is already detailed (base64 id from wave_list_businesses or bare UUID). The description adds the override behavior—the parameter always takes precedence over the default—explaining a semantic not present in the schema, which raises value above baseline.

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 and resource: 'Set the business that later tool calls use when none is given.' It clearly differentiates from the sibling get/list tools by positioning itself as a connector-state setter rather than a Wave API operation, making the purpose unmistakable.

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?

Clearly explains when the tool applies ('when none is given') and lists an alternative behavior—'Passing business_id explicitly always overrides it.' It implies the use case of setting a long-lived default for subsequent calls, though it does not explicitly say 'use this only if you make multiple business-scoped calls' or list non-use conditions. Still clear context without exclusions.

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