odoo_web_login

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

With no annotations, the description carries full burden. It discloses creation of a persistent cookie session, reuse, and lifecycle (until logout or expiry). It does not mention security considerations like credential handling, but covers key behavioral traits.

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?

Three sentences, each conveying essential information: action, session benefits, and reuse behavior. No wasted words, well-structured and easy to parse.

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 explains input and behavior but does not describe the output (e.g., success/failure, session token) or error conditions. Given no output schema, this leaves the agent guessing about return values. Adequate but with clear gaps.

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 80% (4 of 5 parameters have descriptions). The description adds little beyond stating 'user/password' and does not provide additional details for parameters like connection, url, or db. Baseline 3 is appropriate as schema does most of the work.

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 tool logs into the Odoo web interface with user/password and creates a persistent cookie session. It differentiates from sibling tools like odoo_connect and odoo_web_logout by specifying that this session is for accessing web controllers, exports, reports, and frontend URLs.

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 implies usage for scenarios requiring persistent web access to Odoo, and mentions session reuse until logout/expiry. However, it does not explicitly state when to use this tool versus alternatives like odoo_connect, or when not to use it.

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