odoo_sales_summary

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

The description adds useful context (default source, inclusive dates) but does not disclose output format or whether it is read-only. Since annotations are absent, more detail on behavior (e.g., no destructive action) would help.

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?

Single sentence, no unnecessary words, efficiently communicates the tool's function.

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 mentions output (total revenue and order count) but lacks details on format (single object, two fields?), currency, or whether calculations are based on confirmed orders. Adequate for basic understanding but not fully complete.

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 already covers parameters with descriptions (100% coverage). The description adds value by explaining the overall purpose and default source, but does not significantly enhance individual parameter meaning beyond the schema.

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 it computes total revenue and order count over a date range, with source selection (sale or POS). It distinguishes this aggregate tool from sibling tools like odoo_search_read or odoo_overdue_invoices.

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 implies when to use (for summary metrics over a date range) and notes the default source. It does not explicitly exclude alternatives, but sibling names make the distinction clear.

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