odoo_dashboard_inspect

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

No annotations are provided, so the description carries full responsibility for disclosing behavior. It mentions the output is 'en clair' (plain language), but it does not state whether the operation is read-only, what happens if the dashboard_id is invalid, or any permission requirements. This is a significant gap for a tool with no annotation support.

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, front-loaded sentence that immediately states the verb and resource. It is concise and contains no filler, earning a high score for efficiency.

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?

With only one parameter and an output schema present, the description provides a basic but adequate overview. However, it lacks context about prerequisites (e.g., the dashboard must exist) and what the plain-language output actually looks like. It is minimally complete for a simple inspection tool but leaves room for improvement.

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%, and the description does not mention the dashboard_id parameter at all. While the schema's title 'Dashboard Id' gives basic meaning, the description fails to explain how the parameter relates to the tool's function or provide any additional context about selecting a specific dashboard.

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 describes a dashboard's content (charts, sources, filters) in plain language. The verb 'décrire' and resource 'tableau de bord' are specific. It implicitly distinguishes from siblings like odoo_dashboard_list and odoo_dashboard_create, though it does not explicitly name alternatives.

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 offers no guidance on when to use this tool versus alternatives such as odoo_dashboard_list or odoo_dashboard_create. The usage context is only implied from the word 'inspect' in the tool name, not spelled out in the description.

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