Inspect Odoo schema

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

Annotations already declare readOnlyHint=true and idempotentHint=true, so the safety profile is covered. The description adds the 'exposed' qualifier and the conditional behavior based on the model parameter, which is useful, but it does not disclose anything beyond what the annotations plus the simple binary behavior imply.

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?

A single sentence that front-loads the action and clearly presents the two modes with no wasted words. It is compact and immediately scannable.

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 is a read-only schema inspector with only one optional parameter, annotations covering safety and idempotency, and an output schema defining return values, the description is sufficient for correct invocation. Minor omissions like model name format are not critical for this simple 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 0%, so the description must carry parameter meaning. It does explain that providing a model returns field definitions and omitting it lists models, but it does not specify the expected model name format (e.g., 'res.partner' vs 'res_partner') or explicitly state null behavior.

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 states a specific action on a specific resource: listing exposed Odoo models or returning field definitions for a given model. It clearly distinguishes this from data-manipulation siblings like aidoo_create and aidoo_write, though it does not explicitly name an alternative.

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?

Usage is implied through the two modes described: call without model to list models, or with model to get field definitions. However, there is no explicit guidance on when to prefer this over aidoo_query or aidoo_read, nor any exclusions or prerequisites.

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