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

The annotations already state openWorldHint=false and destructiveHint=false, so safety is covered. The description adds important stateful context that the selection affects subsequent Odoo calls, but it does not disclose persistence scope, invalid-workspace behavior, or whether the previous workspace can be restored.

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 definition is a single front-loaded sentence that states the action, resource, and downstream effect with no filler. Every part of the sentence contributes to correct tool selection or invocation.

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 context-setting tool with a fully documented schema and existing annotations, the description is largely complete. It explains the tool's effect on later calls, though it could add a brief note about session persistence or expected behavior for an unknown workspace.

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 100%, and the schema itself explains that workspace accepts an exact slug or a case-insensitive partial name match. The description adds no parameter-level detail beyond that, so the baseline of 3 is appropriate.

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 uses a specific verb pair ('Select or switch') and names the exact resource ('active Tuqui workspace'), plus it states the effect on subsequent Odoo tool calls. This clearly distinguishes it from the many Odoo operation and Tuqui helper siblings.

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?

It gives clear usage context by saying the selected workspace applies to 'subsequent Odoo tool calls,' which implies it should be used before Odoo operations. It does not explicitly state when not to use it or name alternatives, but none of the siblings appear to be a direct alternative for this context-setting role.

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