odoo_web_request

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

No annotations provided. Description lacks details on side effects (e.g., mutations), authentication requirements beyond 'via web session', rate limits, or error handling. For a raw HTTP tool, more behavioral disclosure is needed.

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?

Single sentence is concise but omits critical details. Front-loading is acceptable, but the sentence tries to cover too much without structure.

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 no output schema and many sibling odoo_web_* tools, the description is incomplete. It does not describe return values, error handling, or how it differs from similar tools with overlapping names.

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?

Description adds no information about parameters beyond the schema. With 60% schema coverage and nested objects, the description should clarify usage of 'data' and 'params', but it does not.

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?

Description clearly states it is a 'raw HTTP request' to Odoo controllers, with examples of frontend pages and custom routes. However, it does not explicitly differentiate from sibling tools like odoo_web_call or odoo_web_read.

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 on when to use this tool versus alternatives. Does not mention prerequisites, security considerations, or contrast with sibling tools like odoo_web_call or odoo_web_read.

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