Read Skill

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

Annotations already indicate readOnlyHint=true and destructiveHint=false. The description adds value by stating that the tool returns cloud SKILL.md content without installing or materializing files locally, which clarifies behavioral traits beyond annotations. No contradiction.

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-loading the main purpose in the first sentence with no redundant information. 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 read tool with one parameter and strong annotations, the description is complete: it specifies what is returned (SKILL.md content), what is not done (no local installation), and the prerequisite tools. No output schema is needed as the return value is clarified.

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?

The schema covers 100% of parameters with a description identical to the tool description's implication. The tool description does not add new meaning to the parameter beyond referencing the source of the skill_id. Baseline score of 3 is appropriate.

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 that the tool reads the approved snapshot for one Pathrule skill. It specifies the verb 'Read' and the resource 'approved snapshot for one Pathrule skill', and distinguishes from sibling tools like pathrule_read_snapshot by focusing specifically on skills.

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 advises to use this tool after pathrule_get_context, pathrule_goto, or pathrule_get_node returns a skill_id, providing clear when-to-use guidance. It lacks explicit alternatives or when-not-to-use, but the context is strong enough to guide decision-making.

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