odoo_website_list_page_snippets

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

The description details parsing method (lxml), attributes searched (data-snippet), and output fields (index, xpath, etc.). No annotations exist, so the description carries the full burden and does it well, though it could mention side effects or auth needs.

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 paragraph with the core purpose front-loaded. It efficiently explains the tool without extraneous words, though the list of target fields could be structured.

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?

Given the complexity of parsing multiple models and no output schema, the description provides sufficient context about inputs and outputs. It does not cover error handling or limitations, but is complete for basic usage.

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 coverage is only 40%, so the description should compensate. It adds meaning for field_name by listing valid values, but does not explain connection, model, res_id, or lang beyond the schema. The model and res_id are somewhat inferred but not explicit.

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 lists snippets in an HTML field and specifies target models and fields. It distinguishes itself from sibling tools like odoo_website_add_snippet by focusing on listing, not modification.

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 like odoo_website_list_snippets or when not to use it. The description lacks context on prerequisites or competing tools.

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