odoo_fields_get

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

No annotations are present, so the description carries the full burden. It lists the fields returned and implies a read-only operation, but it does not explicitly state that it modifies nothing nor does it mention any permissions, side effects, or rate limits. The word 'List' suggests safety, but explicit confirmation is missing.

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?

Two concise sentences with no filler. The first states the tool's purpose and return content, while the second offers actionable usage guidance. Every word earns its place.

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 one parameter and no output schema, the description compensates by listing the specific attributes returned and providing a use case. It does not describe the exact response structure (e.g., list vs. map) or error behavior, but for a simple introspection tool, this is reasonably complete.

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 only parameter 'model' has no schema description, and the description only says 'on an Odoo model.' It does not clarify the expected format (e.g., technical model name like 'res.partner') or whether it must be a string. The description adds minimal value beyond the parameter name.

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 immediately states 'List every field on an Odoo model' with a specific verb and resource. It enumerates the output attributes (type, label, required, readonly, relation target, selection options), clearly distinguishing it from sibling tools that search or create records.

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 second sentence explicitly tells when to use the tool: 'Use this before create/write on an unfamiliar model instead of guessing field names.' This provides clear contextual guidance, though it does not explicitly mention when not to use it or name an alternative tool.

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