connection_test

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

With no annotations, the description carries the full burden and discloses almost nothing: it doesn't say whether a failed check throws an error or returns a failure status, whether it times out, or what auth is required beyond 'authorized'. Only the read-only nature is weakly implied by 'check'.

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?

A single front-loaded sentence with no filler. Efficient, though the terseness is partly the cause of the missing detail rather than a virtue on its own.

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 connectivity-check tool the most important information is what a result looks like (success/failure signal), and there is no output schema and no description of the return. Combined with an undocumented parameter, the definition is not complete enough to invoke confidently.

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 0%, so the single required parameter 'connection_id' is completely undocumented. The description does not clarify where this ID comes from (presumably connection_list) or what format it takes, leaving the parameter semantically opaque.

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 states a specific verb and resource ('Check connectivity to an authorized Odoo instance'), making the purpose immediately clear. It doesn't explicitly differentiate from sibling tools like connection_list or server_info_get, which also deal with connections, so it stops short of a 5.

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?

There is no guidance on when to use this versus connection_list or server_info_get, and no stated preconditions or exclusions. Usage can only be inferred from the name, which is weak for a validation-style tool.

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