clients_sync_invoices

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

Goes well beyond the annotations by disclosing what actually changes (name, CUI, tax details written into older invoices), the exclusion boundary (ANAF-uploaded and cancelled invoices are untouched), and the side effect that cached XML/PDF are invalidated and regenerated. It also states the return value (count of invoices updated), which the absence of an output schema makes necessary. No contradiction with destructiveHint=false, since only unsubmitted, non-cancelled drafts are rewritten and the operation is idempotent.

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?

Three tight sentences, front-loaded with the action and scope, then the differentiation, then side effects and return value. Every sentence carries distinct information with no repetition of the name or title.

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 two-parameter mutation tool with annotations and no output schema, the description covers scope, preconditions, side effects, and the return value. An agent has everything needed to decide whether to call it and what to expect.

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 100%, with both uuid and companyId documented inline including the active-company fallback behavior. The description adds no parameter-level detail beyond schema, so the baseline 3 applies.

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 with precise scope: resync all unsent invoices with the client's current profile data (name, CUI, tax details). It also contrasts with the automatic propagation path on client update. The one gap is that the near-identically named sibling invoices_sync_client is never addressed, so an agent must still guess between the two.

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?

Gives concrete eligibility conditions: only invoices not uploaded to ANAF and not cancelled, and explains that it reaches older invoices that automatic propagation does not. Missing is an explicit statement of when to prefer invoices_sync_client or clients_update instead.

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