knowl_skill_read

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

The annotations already declare readOnlyHint=true, and the description aligns with that by describing a read-only operation. It adds useful behavioral context beyond annotations by specifying the exact filesystem location and the files the operation covers, which helps the agent predict the tool's scope and output without contradicting annotations.

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 with no filler: the first states what the tool does, and the second explains when and why to use it. The core action and resource are front-loaded, and 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 simple single-parameter read tool with readOnlyHint=true and no output schema, the description is complete: it names the path, the files read, and the intended usage sequence. No additional information is necessary for an agent to select and invoke this tool correctly.

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 parameter is already described as 'Skill package name.' The description adds mild value by mapping `name` to the `<name>` path segment in `.knowl/skills/<name>/`, but it does not substantially extend the schema's own documentation.

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 states a specific action ('Read'), a concrete resource (`.knowl/skills/<name>/`), and the exact contents included ('skill.json' and 'SKILL.md'). It also clearly differentiates this from knowl_skill_run and knowl_skill_list by framing it as reading a skill package rather than listing or executing one.

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 gives explicit usage guidance: read a skill before running it. It names the related tool knowl_skill_run and explains why this ordering matters ('executes an entrypoint you have seen rather than one you guessed at'), providing both a when and a rationale.

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