Odoo.sh project overview

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

The annotations already declare readOnlyHint=true and destructiveHint=false, and the description does not contradict these. It also mentions the required session ID, making the operational prerequisite transparent. No hidden side effects are implied.

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, using two sentences to convey the action, purpose, and prerequisite. There is no redundant information, and the key points are front-loaded: what it does and when to use it.

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 high-level overview purpose, the description sufficiently outlines the returned information (repositories, branches, environment stages, last build info). It also provides the essential prerequisite (session ID) and usage hint. Since no output schema is provided, the description does not need to specify return formats.

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 'project' has a clear description in the schema: it is a filter with a default value derived from an environment variable or all projects. This fully explains the parameter's meaning and behavior, so no additional description is needed.

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 specific action ('Get repositories, branches and their environment stage with last build info') and the resource (Odoo.sh platform API). It also adds a clear purpose ('Use this first to understand the project layout') that distinguishes it from more targeted sibling tools like odoo_sh_list_builds or odoo_sh_logs.

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 provides an explicit usage condition ('Use this first to understand the project layout') and a prerequisite ('Requires ODOO_SH_SESSION_ID'). However, it does not explicitly mention alternatives or specify when not to use this tool, though the 'first' guidance implies a certain ordering.

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