Read Hermes skill file

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is well covered. The description adds value by disclosing path resolution behavior and root-bounding constraints, which are meaningful behavioral details not present in annotations. It also implies a max_bytes limit via the schema, but the description itself doesn't mention truncation behavior.

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 a single focused sentence with zero waste. Every word contributes to understanding scope and constraints. Front-loaded with the primary action and resource.

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?

With 7 parameters, 0% schema coverage, and an output schema, the description should explain how the skill location resolution works across source/home/profile/toolkit_root since these determine which skill file gets read. The resolved-path concept is hinted but not elaborated. The description is adequate for basic understanding but leaves location semantics unexplained.

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 0%, and there are 7 parameters. The description mentions 'skill' and 'linked file' which map to skill_id and file_path, but doesn't explain the meaning of source, home, profile, or toolkit_root — parameters that distinguish how the skill is located. With 0% schema coverage, the description must compensate for these but only partially does.

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 the tool reads 'one bounded SKILL.md or linked skill file' after resolving the skill and linked file within allowed roots. The verb 'Read' plus resource is clear, and the mention of bounded/root resolution adds specificity. It doesn't explicitly distinguish from siblings, though siblings include read-like tools (hermes_api_docs_read), so differentiation is somewhat implicit.

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 phrase 'within allowed roots' and 'bounded' implies there are constraints on what can be read, providing some security context. However, it doesn't explicitly state when to use this tool versus the many siblings (e.g., hermes_skills_list for listing, hermes_api_skills_list, hermes_skill_eval_start). No explicit exclusions or alternatives are named.

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