odoo_report

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

No annotations provided. The description only states the tool generates a PDF and returns base64, without disclosing side effects, permissions, or safety implications. This is insufficient for a tool that likely requires read access to records.

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 fluff. Efficiently communicates the core purpose and return format.

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?

The description is minimal. Given three parameters (two required) and no output schema, it lacks details on how to use the returned PDF, what report names are valid, or how the 'connection' parameter influences behavior. Basic but acceptable for a straightforward 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 description coverage is only 33% (only 'report_name' has a description). The tool description does not add meaning for 'ids' or 'connection'. With low coverage, the description should compensate but fails to clarify that 'ids' are record IDs or how 'connection' affects operation.

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 generates a PDF report for records and returns base64-encoded PDF. It distinguishes from some siblings by specifying the return format, but does not explicitly differentiate from similar tools like 'odoo_web_report'.

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. The description lacks context about prerequisites, suitable report types, or exclusion criteria.

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