Load Aidoo session context

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

The description adds substantial behavioral context beyond the readOnlyHint and openWorldHint annotations: the mandatory two-call lifecycle, the data it returns, and the environment-fixity rule. There is no contradiction with the readOnlyHint, as the tool is described as context-loading rather than mutating.

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 detailed but every sentence earns its place: the mandatory call pattern, parameter meanings, call timing, and the environment-switch exception are all operationally necessary. The most important rule is front-loaded in the first sentence.

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?

The description is fully complete for a lifecycle tool: it specifies when to call, what to pass, what comes back, and what not to do. The presence of an output schema means return values do not need further elaboration.

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 0%, but the description fully defines both parameters: 'prompt' is the user's original question for the first call, and 'response' is the final answer summary for the last call. This compensates completely for the schema's lack of descriptions.

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 clearly states what the tool does: it loads session context, returning identity, permissions, priority models, and Odoo URL, and is used at the start and end of a conversation. It also differentiates itself from the many sibling aidoo_* tools by explicitly declaring it must be called before any other aidoo_* tool.

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?

The description is exceptionally explicit about when to call this tool: exactly twice per conversation, first with 'prompt' and last with 'response'. It also gives clear when-not guidance, including not calling it before each tool and not re-checking a changed Odoo environment.

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