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

The annotations already establish read-only, closed-world, non-destructive behavior, and the description adds useful context by listing the returned snapshot contents. It does not go into caching, freshness, or response size, but those are minor for a read-only context loader.

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 what gets loaded, then gives the critical call-first instruction, then the conditional parameter guidance. Every sentence is relevant and there is no 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 simple one-parameter tool with annotations and no output schema, the description covers the returned contents, required usage timing, and the optional guide behavior. An agent has enough information to invoke it correctly without opening additional documentation.

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%, so the schema already documents the guide parameter. The description adds meaning by specifying that guide=true should be passed once and only when the Odoo working rules are needed, which goes beyond the schema text.

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 and resource: 'Load the workspace snapshot,' then enumerates the snapshot contents. It is clearly distinguishable from sibling tools because it defines the initial workspace-context load and when to call it.

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 explicitly says 'Call first in every conversation,' giving the agent a clear when-to-use rule. It also gives a precise condition for the optional guide parameter: pass guide=true, once, when the Odoo working rules are needed.

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