trigger_external_sync

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

With no annotations, the description carries the full behavioral burden. It discloses the target surface but says nothing about whether the sync is synchronous or fire-and-forget, whether it consumes quota, auth/connection prerequisites, or side effects from refreshing external data.

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 sentence, front-loaded with the action and immediately followed by the supported scope. Nothing redundant or padded.

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?

An output schema exists, so return values need no explanation. For a one-parameter mutation-style trigger this is close to sufficient, but the undefined parameter values and unstated async/blocking behavior leave gaps for correct invocation.

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 0% — the single 'integration' parameter has no description and no enum. The description names five integration names but never links them to the parameter or states that 'all' (the actual default) is a valid value, so an agent must guess the accepted input format.

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?

Specific verb ('triggers') plus resource ('synchronization for connected integrations') with an enumerated list of supported integrations (GitHub, npm, Hugging Face, RSS, Notion). The siblings (get_profile_context, append_note, etc.) are unrelated profile tools, so no differentiation is needed or attempted, but the purpose itself is unambiguous.

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?

'On-demand' hints at manual invocation as opposed to scheduled syncs, which is implied guidance. However, it never states when an agent should trigger a sync versus relying on background sync, nor any preconditions (e.g., integration must already be connected).

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