odoo_saved_analysis

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

With no annotations, the description carries the full burden of behavioral disclosure. It mentions that 'partage' makes the analysis visible to all and that 'vue' can be pivot or graph, but it does not disclose whether this operation writes data, requires permissions, or has side effects. The core behavior (saving vs. reading) is ambiguous.

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 short and uses a line break to separate the main concept from parameter hints, which is somewhat structured. However, the first sentence is a definition rather than an action statement, and the content is under-specified. It is concise but not optimally effective.

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 tool has 7 parameters, 0% schema coverage, and no annotations, the description should provide more context about what the tool does, when to use it, and what parameters mean. It only partially covers two parameters and gives a vague comparison to dashboards. The output schema exists but the description does not clarify the tool's operation or return value.

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 must compensate. It adds meaning for 'vue' (pivot or graph) and 'partage' (visibility), but leaves five other parameters (nom, model, domaine, groupby, mesures) unexplained. This is partial compensation but insufficient for a 7-parameter tool.

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 is a definitional statement ('Favori Odoo : analyse que le client retrouve...') rather than an action verb. It does not explicitly state whether the tool creates, retrieves, or updates a saved analysis. The name suggests saving, but the description does not confirm. This is closer to tautology than a clear purpose.

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 phrase 'Plus leger qu'un tableau de bord' provides an implicit comparison to dashboards, hinting that this tool is for lightweight saved analyses instead of full dashboards. However, it does not name specific sibling tools or provide explicit when-to-use/when-not-to-use guidance, so it is only implied usage.

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