odoo_status

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

With no annotations provided, the description carries full burden for behavioral disclosure. It indicates the tool reads connection info, which implicitly suggests a non-destructive operation, but it does not explicitly state that it makes no changes, nor does it mention any prerequisites or error conditions. The lack of explicit safety language is a gap, though the 'status' wording helps.

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 one short, front-loaded sentence that immediately conveys the tool's purpose and key outputs. Every word adds value, with no filler or redundancy.

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?

For a zero-parameter status check with an output schema present, the description lists the essential information it returns (database, user, version, read/write mode) and is complete given the tool's simplicity. The presence of an output schema means the description need not detail return values.

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?

The tool has zero parameters, so the baseline is 4. The description doesn't need to explain parameters and doesn't; the schema coverage is trivially 100% with an empty properties object. Nothing more is needed.

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 reports the status of the current connection, listing specific attributes (database, user, version, read/write mode). This is a specific, resource-focused purpose that distinguishes it from siblings like odoo_connect or odoo_enable_write, which handle connection setup or write-mode changes.

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 when to use this tool (to check connection status), but doesn't explicitly mention when not to use it or why it might be preferred over alternatives. There's no reference to related tools or exclusion of cases where another tool would be more appropriate, leaving the decision to the agent's inference.

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