generate_addon

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

With no annotations, the description carries the full behavioral burden. It discloses that the output is a starter, lists its contents, and warns it is not production-ready. However, it does not state whether the tool writes files, returns a bundle, overwrites existing content, or requires any environment setup.

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 sentences, no filler, and the most important qualifier ('Starter only') is front-loaded. Every clause adds useful information.

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 covers the core purpose and safety posture, and the file-component list gives a sense of the deliverable. But with no output schema, no annotations, and two undocumented parameters, it is missing detail on what the generated starter looks like, how optional parameters affect the result, and what the next steps beyond staging install should be.

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 only 33%, and the description does not compensate for the undocumented guardrails and odoo_version parameters. It adds some context around the requirement ('composed from the requirement') but leaves two of three parameters effectively unexplained.

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 names a specific verb ('Generate'), a concrete resource ('an 11-file Odoo addon starter'), and enumerates the file categories involved (manifest, models, views, security, tests, README). It is immediately distinguishable from siblings like validate_addon, draft_plan, or save_addon.

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 'Starter only — review + staging install before production' phrase clearly communicates that this tool is for scaffolding, not final delivery, and implies a follow-up workflow. It does not explicitly name alternatives or state when to prefer draft_plan or save_addon, but the usage context is clear enough.

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