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

No annotations are supplied, so the description carries the full burden. It does usefully disclose that deduplication and conflict resolution happen, which is real behavioral context beyond the schema, but it omits whether the operation overwrites existing axioms, what permissions it needs, whether it is idempotent, and what it returns.

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?

A single dense sentence with no filler, front-loaded on the action and its output. It is jargon-heavy ('Axiomat', 'Small World') but that terminology is consistent with the surrounding tool family.

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 five-parameter write tool with a nested payload object, no annotations, and no output schema, one sentence is thin. The agent still lacks input-mode guidance, mutation/overwrite semantics, and any indication of the result shape, though the deduplication and conflict-resolution hint covers part of the behavioral surface.

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 coverage is 100%, so the baseline is 3, and the description adds a little by framing text vs payload as two source modes and tying conflict resolution to the ingest step. It stops short of clarifying the key ambiguity the schema leaves open: neither text nor payload is required, so nothing tells the agent which one to supply.

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 pair (extract and synchronize) and a specific resource (atomic axioms) with a named destination (a Small World via Axiomat). This is clearly distinguishable from read-oriented siblings like syntropy_get_world_axioms and syntropy_list_worlds, though it never names 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?

The description offers no when-to-use guidance, no prerequisites, and no alternatives. It says axioms can come from 'raw text or a JSON record' but never states when to choose one input mode over the other, nor whether they are mutually exclusive – which is exactly the decision an agent faces at call time.

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