odoo_fp_configure

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 implies mutation ('Add or update') but doesn't disclose side effects, authentication needs, or rate limits. It does specify the create/update branching logic, which adds some transparency.

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 with no fluff. First sentence states purpose and logic, second provides a helpful reference. Every word earns its place.

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 13 parameters, create/update logic, and no output schema, the description is fairly complete. It covers the core logic but could mention that l10n_bg_narration is required for create (though present in schema). Still adequate for an AI agent.

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 92%, so baseline is 3. The description adds value by explaining the create/update logic and pointing to odoo_fp_types for selection values, which goes beyond the parameter descriptions in the schema.

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 it 'Add or update a tax action map entry for a fiscal position', distinguishing between create and update via action_id or position_id. It also references the related tool odoo_fp_types for selection values, making it easy to understand the tool's specific function.

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 explicit guidance: use action_id to update existing entry, position_id to create new. It points to odoo_fp_types for selection values. While it doesn't contrast with sibling tools, the purpose is distinct enough that no further differentiation is needed.

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