verify_odoo_live_metadata

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

With no annotations, the description does useful work by declaring the transport is read-only XML-RPC, that credentials are required, and that the timeout defaults to 10 seconds. It does not say what happens when a model/field is missing (error vs. reported as absent), nor what the response looks like, which matters for a verification call whose whole value is its verdict.

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 opening sentence front-loads the core action and the Args block is scannable with no filler. Slightly verbose in the example-heavy parameter lines, but every example disambiguates a format the schema leaves opaque.

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?

No output schema exists, so the description must characterize the return value and it does not—an agent cannot tell whether it receives booleans per item, a list of missing IDs, or raises on failure. Inputs are fully covered; the result contract is the remaining gap for an 8-parameter verification tool.

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 0%, so the Args block carries the full load and does it well: each of the 8 parameters gets meaning, format, and concrete examples (URL shapes, model names, the fields mapping structure, XML ID samples, timeout default). An agent could construct a correct call from this alone.

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: connect to a live Odoo instance over read-only XML-RPC and verify models, fields, and external XML IDs. That is clearly distinct from the static-analysis siblings, though it never names them explicitly to reinforce the split.

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 phrase 'running Odoo instance' and 'dynamically verify' imply this is for live-environment checks rather than static file inspection, but there is no explicit when-to-use guidance, no exclusions, and no reference to the sibling tools that analyze code statically.

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