validate_odoo_manifest

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

No annotations are provided, so the description carries the full burden. It usefully discloses the checks performed (manifest syntax, important fields, data/demo file existence), but does not state that the operation is read-only or describe the validation result shape.

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 compact sentences plus a short Args note; the validation checks are front-loaded and every line adds useful information given the bare schema.

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?

Input semantics are covered, but with no output schema the description should explain what a validation result looks like; it does not. With no annotations and no sibling differentiation, the definition is only adequately complete for invocation.

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 sole parameter has 0% schema description coverage, and the description compensates by naming it and specifying it is an absolute path to the addon directory. This is sufficient to invoke correctly, though it adds no example path or format detail.

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?

States a specific verb and resource: validates an Odoo addon manifest plus declared data/demo files. It clearly defines scope, but does not explicitly distinguish itself from siblings such as check_odoo_addon_health or inspect_odoo_module.

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 gives no explicit when-to-use, when-not-to-use, or alternative guidance. An agent can infer it is for manifest validation, but must guess how it differs from sibling tools like check_odoo_addon_health.

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