ck_load_resources

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false. The description adds that loading can be bulk and 'governed,' but does not disclose additional behaviors like authentication needs or rate limits. The annotation coverage reduces the burden, but the description adds moderate value.

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?

The description is two sentences, front-loaded with the fallback purpose, and every word adds value. No redundancy or fluff.

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?

The description covers the main purpose and bulk loading capability. With an output schema present and annotations covering safety, the description is adequate for an AI agent to understand the tool's primary use case, though it does not detail all parameters beyond uris.

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 75%, with session_id lacking a description. The description provides a URI format example (skills://<name>) that adds clarity to the 'uris' parameter, but it does not compensate for the missing description of session_id. Overall, the description adds some meaning but does not fully offset the schema gap.

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 clearly states the tool loads CK resource URIs, especially skills, and explicitly positions it as a fallback for clients that do not support MCP resources or native bulk skill loading. This distinguishes it from sibling tools like ck_skill_load and provides a specific verb and resource.

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 description explicitly states when to use this tool: 'Fallback for clients that do not support MCP resources or native bulk skill loading.' This provides clear context but does not name specific alternative tools, leaving some room for interpretation.

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