odoo_website_remove_snippet

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

The description discloses the core behavior: removes a snippet and writes back reduced HTML. This implies a destructive write operation. However, without annotations, it lacks details on side effects, permissions, or error handling. The presence of a 'dry_run' parameter is not mentioned in the description.

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 concise sentences with no redundancy. The action, location method, and effect are clearly stated. Every word contributes value.

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?

Despite the concise purpose, the description is incomplete for a 7-parameter tool with no annotations and no output schema. It omits explanation of key parameters and usage context, making it hard for an AI agent to correctly invoke the tool without additional knowledge.

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?

Only 'snippet_xpath' is partially described (absolute). The other 6 parameters (connection, model, res_id, field_name, lang, dry_run) are not explained in the description. With 0% schema description coverage, the description fails to add meaning to most parameters.

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 action ('Remove a snippet block') and the target resource ('from a target HTML field'). It is specific and distinct from sibling tools like add_snippet, update_snippet, or list_snippets.

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?

No guidance on when to use this tool versus alternatives. It does not mention prerequisites (e.g., obtaining snippet_xpath) or scenarios where removal is not advisable. The phrase 'Locates via snippet_xpath (absolute)' hints at known XPath requirement, but no explicit context provided.

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