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

Annotations already establish it is a non-read-only, non-destructive write; the description adds the useful behavior that existing composition/families/price are overwritten from the current source. However it does not say whether manual edits are lost, whether the change is reversible, or note that idempotentHint is false, so transparency is incomplete for a data-overwriting operation.

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?

One tightly front-loaded sentence that puts the usage condition first and the effect second, with no filler. The trailing 'as the app's Re-sync does' is slightly redundant but does anchor the behavior to a known UI action.

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 with no output schema, the description covers trigger and effect but omits outcome-relevant details such as what happens on failure, whether manual overrides survive, and reversibility. Adequate but with clear gaps.

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%, so both parameters (line, formula) are already documented with id/name formats. The description loosely corroborates 'source formula' and 'accord line' but adds no new syntax or constraint detail beyond 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 names a specific verb (re-reads/re-sync) and resource (the accord line), and states exactly what fields are refreshed: composition, families, and price. That distinguishes it from siblings like view_accord (no mutation) and update_formula (manual edit), though it doesn't name a sibling explicitly.

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?

It gives an explicit trigger condition: use when the source formula has changed and the user wants the accord line to follow. This is real when-to-use guidance, but it names no alternative tool or a when-not condition (e.g. versus edit_formula).

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