odoo_search_count

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

With no annotations, the description must cover behavioral traits. It only states the basic action. It does not disclose that the tool is read-only, whether it has performance implications, or that it returns a single integer. The description lacks important behavioral context beyond the core function.

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 sentence, directly stating the tool's purpose with no extraneous words. It is well-structured and front-loaded.

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 Odoo context and numerous sibling tools, the description is incomplete. It does not explain the return value (a count number), the expected domain format, or how it differs from similar tools. Without an output schema, the description should at least clarify what the tool returns, but it does not.

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%, so the description should explain parameter meanings. While 'domain' is mentioned in the description, there is no explanation of what a domain is (e.g., Odoo domain syntax) or details about 'model' and 'connection'. The description adds minimal value over the parameter names alone.

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: count records based on a domain. It is specific and uses a verb+resource format. However, it does not distinguish from sibling tools like odoo_search or odoo_search_read, which might perform similar but different operations.

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 provides no guidance on when to use this tool versus alternatives. It does not mention that this is purely for counting, while odoo_search retrieves records, or that it should be used when only the count is needed. No when-not-to-use or context is given.

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