nexterm_sync_source

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

Annotations already establish this is a non-read-only, non-idempotent, open-world operation, so the safety profile is partly covered. However, the description adds nothing about what synchronization actually does — whether it overwrites existing content, runs asynchronously, can fail partway, or makes network calls that may be slow or rate-limited. For a non-idempotent write with external effects, that is a meaningful gap.

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 front-loaded sentence with no filler, so it is structurally clean. But brevity here comes at the cost of under-specification rather than efficiency — the sentence is too thin for a non-idempotent write operation.

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?

With no output schema, 0% parameter coverage, and no explanation of the sync semantics or return value, an agent cannot confidently predict the outcome of calling this tool. The description should at minimum state what gets synchronized and what a caller receives.

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% — source_id is documented only by its name and a minimum of 1. The description's phrase 'one Nexterm content source' implies the parameter selects a single source, but it adds no format, constraint, or validation detail beyond what the schema already shows.

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 has a clear verb and resource ('Synchronize ... source'), but 'synchronize' is undefined — it doesn't say in which direction (pull/push), what content is affected, or what the result is. It fails to distinguish itself from close siblings like nexterm_sync_all_sources, nexterm_validate_source, or nexterm_sync_integration.

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 guidance on when to use this versus nexterm_sync_all_sources or nexterm_sync_integration, and no preconditions (e.g. source must be validated/connected first). The word 'one' hints at single-source scope, but the agent must infer it from the sibling names rather than the description.

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