odoo_website_list_snippets

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

No annotations exist, so the description carries full responsibility. It discloses the return structure and mentions inference logic for categories, adding some behavioral context. However, it does not mention read-only nature, authentication requirements, or any side effects, which are important for undisclosed behaviors.

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, no redundant wording. Front-loaded with the core purpose and quickly covers return details, making it efficient for an agent to parse.

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 no output schema, the description adequately explains return fields. It lacks mention of pagination or the effect of the 'limit' parameter, but overall provides sufficient context for a discovery tool.

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 covers 60% of parameters with descriptions; the description itself adds no parameter-level detail beyond that baseline. It focuses on return fields rather than parameter meaning, so it does not compensate for the uncovered schema parameters significantly.

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?

Clearly states the tool lists available Odoo website snippet templates, specifying the exact domain (ir.ui.view records with key matching 'website.s_*') and return fields. Distinguishes from sibling tools like odoo_website_add_snippet and odoo_website_list_page_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?

Briefly states 'use this to discover what snippets can be added to a page' but provides no explicit when-not-to-use guidance or comparison to alternatives. Lacks contrast with closely related sibling tools, leaving room for ambiguity.

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