odoo_connect

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

Even though annotations are absent, the description discloses important behavior: credentials are kept in server memory only (never on disk), db is auto-deduced from subdomain when omitted, and allow_write should remain False. This adds meaningful context about credential safety and default 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 three concise sentences, front-loaded with the main purpose ('Se connecter'). Every sentence adds value: usage order, security behavior, and parameter guidance. No redundancy or 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?

Given that an output schema exists, the description needn't explain return values. It covers essential context: first-call requirement, credential handling, db fallback, and allow_write recommendation. It's adequate for a connection tool, though it doesn't mention potential outcomes like session tokens or error conditions, which the output schema likely handles.

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?

With schema description coverage at 0%, the description must compensate. It clarifies the `db` parameter (deduced from subdomain if omitted) and `allow_write` (should be False). However, url, username, and api_key are left to their self-evident names, so coverage is partial.

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 begins with 'Se connecter' (Connect), clearly stating the tool's purpose as establishing a connection. The phrase 'a appeler en premier' (to call first) distinguishes it from all sibling odoo tools by establishing its role as the mandatory initial call.

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 explicitly states when to use this tool: first, before any other odoo operation. It also names an alternative for write permissions ('voir odoo_enable_write'), giving clear guidance on when not to set allow_write to True.

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