Load Skill

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

Annotations already declare readOnlyHint=true and destructiveHint=false, covering the safety profile. The description adds useful behavioral context by noting the load is bounded and path-restricted, but it does not explain response format, truncation behavior, or error handling.

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, no fluff, with the core operation and the most important usage constraint front-loaded. Every clause earns its place.

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 read-only tool with 7 well-documented parameters, the description gives the essential sequence (inventory first, then load by name) and the critical restriction on paths. It does not detail output shape, but 'SKILL.md body' communicates the main return value, and annotations cover safety.

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%, so the schema already documents all 7 parameters. The description adds the key constraint that names come from skill_inventory and that arbitrary paths are rejected, which complements the path/name parameters but does not need to repeat the full schema.

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 a specific verb ('Load') and a specific resource ('bounded SKILL.md body') for discovered workspace, user, or plugin skills. It also distinguishes itself from arbitrary file reading by explicitly rejecting arbitrary paths.

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?

It clearly states the precondition: use after open_current_workspace/open_workspace shows skill_inventory. It also gives a negative guideline ('Does not accept arbitrary paths'), helping the agent know when this tool is not appropriate.

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