odoo_fp_remove_action

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

The description only says 'Remove' without disclosing side effects, reversibility, permissions, or return behavior. With no annotations provided, the burden falls entirely on the description, which is insufficient.

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 a single sentence with no fluff, conveying the core purpose efficiently and front-loading the key 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?

Given the presence of sibling fiscal position tools and no output schema, the description lacks context about what happens after removal, what a tax action map entry is, and how it relates to other operations. The information is insufficient for an agent to fully understand the tool's role.

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 50%; action_id has a description but connection does not. The description does not add any additional meaning beyond the schema for the parameters, failing to compensate for the missing connection description.

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 removes a tax action map entry from a fiscal position, referencing the module l10n_bg_tax_admin. The verb 'Remove' and the resource are explicit, distinguishing it from sibling tools like odoo_fp_list or odoo_fp_configure.

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 no guidance on when to use this tool versus alternatives, and does not mention prerequisites or the context of a tax action map entry, leaving the agent unclear about appropriate usage.

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