odoo_connect

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

With no annotations, the description should fully disclose behavioral traits. It mentions add/update but lacks details on overwrite behavior, validation, side effects, or whether it tests the connection. The agent is left guessing about important operational semantics.

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 two sentences, immediately stating the main purpose and key options. It is front-loaded and contains no superfluous information, earning every sentence it uses.

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 8 parameters and no output schema, the description covers the basic purpose and auth/protocol options. However, it omits details about output (what is returned), workflow integration (how connections are used by other tools), and update mechanism (role of alias).

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 high (88%). The description adds value beyond the schema by clarifying the mutual exclusivity of password vs. API key and the protocol version implications. This compensates for the slight lack of explicit parameter documentation.

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 the verb 'Add/update' and the resource 'Odoo connection', with specifics about authentication methods and protocol versions, distinguishing it from sibling tools like odoo_connections or odoo_disconnect.

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?

No guidance is provided on when to use this tool versus alternatives. It does not mention prerequisites, such as needing an existing connection for update, or suggest using odoo_connections to list existing connections first.

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