diagnose_odoo_call

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and idempotentHint=true, indicating a safe, non-destructive operation. The description adds minimal behavioral context beyond confirming no execution. It does not detail what 'diagnose' entails in terms of output or side effects.

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 efficiently conveys the core purpose. However, its brevity comes at the cost of omitting necessary parameter and behavioral details, making it under-specified for practical use.

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's complexity (10 parameters, 2 required, no schema descriptions) and the presence of a diagnostic output schema, the description fails to explain what the diagnosis returns or how parameters affect behavior. This makes the tool incomplete for accurate invocation.

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?

The input schema has 10 parameters with 0% description coverage, and the tool description provides no information about any parameter meaning. This is a critical gap for an AI agent to correctly invoke the tool, especially for parameters like 'model', 'method', 'args', and 'kwargs'.

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 'Diagnose an Odoo model call without executing it' clearly states the tool's purpose with a specific verb ('Diagnose') and resource ('an Odoo model call'), and distinguishes it from sibling tools like 'execute_method' which executes calls.

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 usage for diagnosing without executing, but lacks explicit guidance on when to use this tool versus alternatives like 'execute_method' or 'preview_write'. No mentions of when-not-to-use or prerequisites.

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