get_skill

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

Describes what the returned JSON contains (name, description, type, quality_score, stars, security_score, safety manifest, install configs for 12 platforms, usage hints). Missing mention of read-only nature, error handling for non-existent slugs, or rate limits, but covers main behavioral aspects adequately.

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, front-loaded with main action, then structured list of returned fields, then usage guidance. No wasted words.

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 no output schema, the description compensates by listing all returned fields. Missing note on error handling for missing slug. Covers usage, param, and return value well.

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?

Parameter 'slug' has 100% schema coverage with description and examples. The description adds extra context: slug format (owner/repo), examples, and advice to use search_skills if slug unknown.

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?

Clearly states it gets comprehensive details for a specific skill by slug. Distinguishes from sibling tools by explicitly stating not to use for discovery (use search_skills or recommend_skills instead).

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?

Explicitly states when to use (when you know exact slug and need full metadata before installing) and when not to use (for discovery), with clear alternatives (search_skills, recommend_skills).

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