sync_skills

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

With no annotations, the description carries the full load and does well: it discloses that this mutates the local checkout ('Writes local files'), that effects are deferred until the next session, and that a not_enrolled status can be returned. It doesn't say whether existing/local skill edits are overwritten or whether the operation is idempotent, which matters for a file-writing tool.

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?

Four short sentences, zero filler, with the core action front-loaded and the prerequisite, side effect, and alternative following in order of importance. Each sentence carries distinct information.

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 zero-param, no-output-schema mutation tool, the description covers prerequisite, side effects, timing, and the sibling alternative. The remaining gap is what a successful return looks like (counts of installed vs updated skills), which there is no output schema to fall back on.

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?

Zero-parameter tool, so baseline is 4, and the description confirms 'Takes no input,' which matches the empty schema. Nothing further is needed.

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 (sync) and a specific resource (managed organization skills) into a named target (this checkout). It also explicitly distinguishes itself from a sibling by saying refresh_decision_pack is for decisions, not skills, so an agent can route correctly without opening schemas.

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?

Gives a hard prerequisite (must be enrolled via lockstep enroll, otherwise not_enrolled) and names an alternative tool for the adjacent use case. What it lacks is a positive trigger telling the agent when in a session to call sync_skills, though 'skills load from the next session' hints it should be early.

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