odoo_module_info

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

No annotations are provided, so the description must disclose behavioral traits. It mentions Odoo RPC state and filesystem locations, but does not explicitly state that a connection (via odoo_connect) is required, or the error behavior if the module does not exist. The safety profile (read-only vs. destructive) is not clarified.

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, front-loading the main action and then elaborating on the returned information. Every sentence adds value with no redundant or vague language.

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, the description hints at return fields (manifest, dependencies, etc.) but omits structure, error conditions (e.g., module not found), or relationship to connection state. For a detailed info tool, this is adequate but lacks completeness.

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 50% ( 'module' parameter has a description, 'connection' does not). The overall description does not add extra meaning to either parameter beyond the schema, such as explaining the 'default' connection value. It does not compensate for the missing parameter description.

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's purpose: 'Get detailed information about an Odoo module' and specifies the exact information retrieved (RPC state, filesystem locations, manifest, dependencies, installation status). It distinguishes itself from sibling tools like odoo_cert_info and odoo_read by focusing on module-specific metadata.

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 when module details are needed but provides no explicit guidance on when to use this tool versus alternatives (e.g., odoo_read for generic records) or prerequisites (e.g., established connection). No 'when not to use' or alternative tool recommendations are given.

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