update_income

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

The description warns about destructive effects (destructiveHint=true) and explains the behavior for income_lines and charges: with ID updates, without ID creates, omitted deletes. This adds valuable behavioral context beyond the annotation.

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?

Very concise single sentence with visual warning. Front-loaded with important safety note. Efficient but could benefit from clearer structure for the array rules.

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 9 parameters (4 required) and no schema coverage, the description provides key behavioral logic for arrays but lacks details on other parameters, error handling, or success conditions. An output schema exists, so return values need not be explained, but overall completeness is moderate.

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 description must compensate. It explains the semantics for income_lines and charges arrays, but other parameters like income_id, customer, date, etc., are not described. Partial compensation.

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 states 'Actualiza ingreso' (update income) with a warning, clearly indicating the verb and resource. However, it is in Spanish and could be more explicit about the overall action, distinguishing it from sibling tools like create_income or delete_income.

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?

No explicit guidance on when to use update_income vs alternatives (e.g., update_income_charges, update_income_attachment). The warning to confirm with user is included, but no context about when not to use this tool.

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