Discover Odoo.sh model fields

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

Annotations already establish read-only, open-world, and non-destructive behavior. The description aligns with these by using 'introspect', but adds no new side-effect or output behavior details. Given the annotations cover the key traits, this is acceptable, though slightly more detail on the response format would have been beneficial.

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 concise and tightly scoped. It leads with the action, provides context, and states the conditional trigger in two sentences without extraneous detail. All content is relevant and contributes to understanding.

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 simple interface (one parameter, no output schema), the description provides complete guidance: what it does, when to use it, and how it connects to downstream tools. It is self-sufficient for an agent to decide when and how to invoke it.

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 single parameter 'model' has full schema coverage with an enum and a basic description ('Model to introspect'). The main description enriches this by listing example values (paas.repository, paas.branch, etc.) and clarifying the domain (Odoo.sh platform model). Some additional semantics per enum value would be helpful, but the provided context is adequate for the tool's purpose.

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?

Clearly states the tool's function: introspecting available fields on an Odoo.sh platform model. Provides concrete examples (paas.repository, paas.branch) and differentiates from siblings by indicating it is a preliminary step before querying with odoo_sh_search_read.

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?

Explicitly conditionally recommends use: 'Use this if odoo_sh_list_builds/odoo_sh_overview return unexpected data'. Also guides the next step ('then query precisely with odoo_sh_search_read'), giving clear when-to-use and how-to-proceed instructions.

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