Get an Agent Skill

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint=false and destructiveHint=false, so the safety profile is covered. The description adds value beyond that by disclosing the returned field set and an install-safety caveat for third-party skills ('review the source before installing'). It does not say what happens on an unknown slug, which keeps it out of the top band.

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, verb and resource front-loaded, with the enumeration packed into a single clause and the third-party warning isolated at the end. The field list is dense but each item tells the agent what to expect back in the absence of an output schema, so it earns its space.

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?

No output schema exists, and the description compensates by enumerating the returned fields plus both URL forms (source and canonical swarmnest.ai). Safety and idempotency are carried by annotations. Only the not-found/error behavior is unaddressed.

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?

With a single parameter at 100% schema coverage the baseline is 3, and the description earns an extra point by clarifying the slug's provenance ('from search_skills') — the schema only gives a maxLength and an example, not how to obtain the value.

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?

States a specific verb and resource ('Get one Agent Skill by slug') and then enumerates exactly what the result contains (summary, format, platforms, install steps, labels, license, author, URLs). It also names the sibling that produces the input (search_skills), so an agent can distinguish it from search_skills/search_directory without opening a schema.

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 parenthetical '(from search_skills)' tells the agent this is the follow-up detail call after a search, which is clear usable context. There are no explicit exclusions (e.g., when to prefer get_entry or list_categories), so it stops short of full alternative routing.

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