odoo_name_find

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

With no annotations, the description carries the full burden, but it only mentions 'autocompletion Odoo' and id conversion. It does not disclose whether it returns a single ID or multiple, what happens if no match is found, whether it is read-only, or any other side effects.

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 a single, focused sentence that immediately states the purpose and includes an illustrative example. It is appropriately sized for its simplicity, though a bit more structure (e.g., separating the use case from the method) could enhance readability.

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?

Although an output schema exists (so return values are likely covered), the description lacks essential context for a tool with three parameters: no explanation of acceptable models, the meaning of 'limit', failure behavior, or how autocompletion works. It is too sparse for reliable agent invocation.

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%, and the description does not explain any of the three parameters (model, name, limit). The mention of 'par nom' relates to the name parameter, but model and limit are entirely undocumented, adding no value over the bare schema.

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 function: 'Retrouver par nom (autocompletion Odoo) — convertir "le client Polytec" en id.' It uses a specific verb (retrouver) and resource (name-to-id conversion), and the concrete example distinguishes it from sibling tools like odoo_read or odoo_search.

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 the use case (when you have a name and need an ID) but does not explicitly state when not to use this tool or mention alternatives. There is no comparison with siblings, so the guidance is minimal and left to inference.

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