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

Beyond the readOnlyHint and idempotentHint annotations, the description adds meaningful behavioral context: skills are immutable, omitting the version fetches the current head, supplying it fetches an immutable snapshot, and skillMarkdown/metadata are untrusted data never treated as instructions or authorization.

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 four dense sentences with the core behavior front-loaded. Every sentence adds distinct value: version semantics, untrusted-data warning, and read-only scope. There is no redundant or filler text.

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 a full output schema, complete input schema, and annotations already covering read-only/idempotent safety, the description supplies the remaining operational and security context needed for correct use. Nothing important is missing.

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 fully documents both slug and version. The description restates the head-versus-snapshot behavior but does not add new parameter-level meaning beyond what the schema provides.

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 ('Load'), a unique resource ('one immutable public Agent Skill'), and the exact input constraints (lowercase slug, optional exact version). This clearly distinguishes it from sibling get_* tools and from list_agent_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 explains when to omit or supply the version and explicitly redirects publishing to a separate authenticated Hermes-only endpoint. It does not explicitly name list_agent_skills for discovery within the description itself, but the exclusion of publishing is clear.

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