odoo_enable_write

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 warns that deletions are irreversible and that user consent is required, which are key safety behaviors. It does not elaborate on the state change or persistence, but the warnings add valuable context.

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?

Two sentences, front-loaded with the action and followed by a critical safety warning. Every word contributes; no fluff.

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 simple toggle with an output schema, the description covers the essential use case and safety warning. It lacks detail on what 'write' encompasses, but the tool name and siblings compensate. Acceptable for a tool of this complexity.

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 schema has one boolean parameter 'enable' with 0% description coverage. The description's 'Activer (ou couper)' directly maps to true/false, providing some semantic interpretation. However, it doesn't explain the default or the exact effects of each value beyond enabling/disabling writing.

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/action ('Activer/couper') on a specific resource ('l'ecriture'), clearly indicating this toggles write mode. It is distinguishable from sibling tools like odoo_write and odoo_unlink, though it does not explicitly name them.

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?

Explicitly states when to call: only after showing the user what will be modified and obtaining consent. This is a clear usage condition. No alternative tools are mentioned, but the safety context is strong.

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