List Odoo.sh builds

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

The description adds the requirement for ODOO_SH_SESSION_ID and emphasizes 'REAL' statuses, which goes beyond the readOnly/openWorld/destructive annotations. No contradictions exist, and it provides useful behavioral context.

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, focused sentence with no redundancy. It efficiently conveys purpose, key details, and a requirement without any fluff.

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?

The description provides enough context for the expected output (builds with statuses), the source (Odoo.sh API), and a prerequisite (session ID). While there is no output schema, the description gives a reasonable idea of what the tool returns.

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 coverage is 100% with clear parameter descriptions for limit and branch. The description reinforces branch filtering but does not add significant meaning beyond the schema, so the baseline of 3 is appropriate.

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 clearly states the tool's purpose: listing recent builds with their actual statuses (success, failed, testing). It distinguishes itself from sibling tools by focusing on builds and mentioning the Odoo.sh API and branch filtering.

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 says 'List recent builds' and mentions branch filtering, which implies when to use it. However, it does not explicitly contrast it with alternatives like odoo_sh_logs or odoo_sh_status, so usage guidance is only implicit.

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