Odoo App Selector

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

With no annotations provided, the description carries full responsibility for behavioral disclosure. It only restates the general purpose and gives no hints about side effects, output format, or limitations. An agent cannot anticipate whether this is a read-only recommendation tool or something more.

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, compact sentence with no wasted words. It is front-loaded with the core purpose. However, the brevity sacrifices essential detail, so it is concise but under-specified.

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 three parameters, no annotations, and no output schema, the description is far too thin. It fails to explain inputs, expected outputs, or behavioral context. An agent invoking this tool would have minimal understanding of what is required or returned.

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 compensate. It never mentions the parameters (needs, users, businessType) or how they influence results. The phrase 'your business needs' vaguely hints at the 'needs' array but provides no detail on usage or constraints.

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 uses a clear verb ('Find') and identifies the resource ('Odoo apps') and the user's need ('your business needs'). This is distinct from the calculator siblings, which focus on numeric computations. However, it doesn't specify the output form (e.g., recommendations) or differentiate beyond the basic 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 description provides no guidance on when to use this tool versus alternatives. It doesn't mention alternatives or exclusion criteria. The name implies its role as an app selector, but the description itself offers no context for selection among the many sibling tools.

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