hibob_update_position_budget

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

Annotations already indicate the operation is not read-only, is idempotent, and is not destructive. The description adds useful behavioral context beyond annotations by specifying the return format (JSON confirmation or error message prefixed with 'Error:') and the rate limit of 10 requests/minute.

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 well structured and front-loaded: a one-line action, lookup guidance, parameter explanations, return behavior, and rate limit. Every section earns its place with no filler or repetition of the annotations.

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?

For a 3-parameter update tool with an output schema, the description is nearly complete: it explains how to find the budget ID, what the fields parameter means, what the response looks like, and the rate limit. It could further clarify whether unspecified fields are left unchanged, but this is largely inferable from 'fields to change.'

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 schema already covers all three parameters with descriptions, so the baseline is 3. The description adds meaningful semantics by explaining that 'fields' is a 'flat mapping of field IDs to new values' and that 'position_id' is the parent position ID, reinforcing the relationship between the required parameters.

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 opens with 'Change an existing position budget,' a specific verb+resource phrase that precisely identifies the tool's function. It also points to hibob_search_position_budgets for finding the budget ID, which implicitly distinguishes this update operation from the search and create siblings.

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 a clear usage step: use hibob_search_position_budgets to find the budget ID before calling this tool. It does not explicitly list exclusions or alternatives beyond that prereq, but the 'existing position budget' wording and sibling names make the intended usage unambiguous.

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