hermes_skill_view

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

Annotations already declare readOnlyHint, destructiveHint, and idempotentHint. The description adds 'Read-only' which is redundant. It discloses no additional behavioral traits (e.g., behavior for missing skill, rate limits, or output details).

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 extremely concise: two short sentences with no unnecessary words. Every part is purposeful.

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?

Given the output schema exists and the tool has only one parameter, the description is largely complete. However, it could briefly mention that the content is specific to a skill's SKILL.md file, which is implied but not explicit.

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 only parameter 'name' has no schema description (0% coverage). The description says 'by name' but does not clarify format, case sensitivity, or provide examples. Minimal value added beyond the 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 clearly states the action ('Read'), the specific resource ('SKILL.md content for one installed Hermes skill by name'), and implicitly distinguishes from sibling tools like hermes_skill_list (which lists skills) and hermes_read_file (which reads arbitrary files).

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 implies usage by focusing on a specific resource ('by name'), but provides no explicit guidance on when to use this tool versus alternatives (e.g., hermes_skill_list for listing skills, hermes_read_file for other files). Minimal context for selection.

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