ck_skill_load

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

Annotations declare readOnlyHint=true and idempotentHint=true. Description adds details on output format (SKILL.md wrapped in <skill_content> tags plus bundled files), which is consistent with read-only behavior. The term 'activate' might imply state change but annotations clarify it's safe.

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?

Two sentences: first states purpose and output, second gives usage order. No fluff; every word contributes. Front-loaded with key 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?

Given complexity of 5 parameters and presence of output schema, the description covers the main usage flow (call after list, output format, bundled resources). Could mention error handling or what happens if skill not found, but sufficient for typical 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 80%. Description adds value by explaining why the name param lacks enums in MCP stdio mode and clarifies project_root behavior (global-only if omitted). However, for most parameters, the schema already provides adequate descriptions.

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?

Description clearly states the tool loads full instructions for a named AgentSkill, returns SKILL.md in XML tags plus bundled resources. It distinguishes from sibling tool ck_skill_list by specifying this is for loading after listing.

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?

Explicitly instructs to call after ck_skill_list to activate a specific skill. Provides clear context on when to use, though does not list alternatives or exclusions.

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