sync_skills_from_github

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 that the default operation pulls from ALDY711/apk-reverse-modifikasi and updates the library, but it does not explain whether local changes are overwritten or merged, which branch or ref is used, authentication or network requirements, or partial-failure behavior.

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 compactly states the action, resource, source, and default repository. There is no filler or structural clutter, and the repeated default remains directly useful for invocation.

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?

Basic invocation is clear for a tool with one optional, fully documented parameter. However, without annotations or an output schema, a mutating network synchronization tool needs more detail about overwrite or merge behavior, source selection and authentication, and success or failure outcomes to support fully reliable use.

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%, and the repo field already documents its URL-or-slug format and default value. The description repeats the default repository but adds no further parameter semantics, so the schema appropriately does most of the work.

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 uses specific verbs (“Sinkronisasi dan perbarui”) and identifies both the resource (“pustaka skills”) and the GitHub source, including a concrete default repository. Its action is implicitly distinct from the list, search, and guide siblings, but it does not explicitly differentiate itself from them.

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 wording implies that the tool should be used when the skills library needs to be refreshed from GitHub. It provides no explicit prerequisites, when-not guidance, or direction to inspection siblings such as list_antigravity_skills or search_skills when synchronization is unnecessary.

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