install_skill

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

No annotations provided, so description carries full burden. States the tool is read-only ('does NOT write any files') and mentions memory side effect. Could add more on required permissions or error conditions, but adequately describes core behaviors.

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?

Four sentences, front-loaded with purpose and return format. Some redundancy (e.g., 'This tool is read-only' repeated from context). Could be tightened but overall efficient.

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, so description compensates by detailing return object fields. Covers side effects (memory save) and limitations. Missing error handling or prerequisites (e.g., authentication), but acceptable given tool simplicity.

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 coverage is 100% with descriptions. Description adds context about return format (config_path, config, instructions) and confirms slug format (owner/repo). Also provides insight into how agent enum values map to platforms (e.g., 'claude-code' for .claude/settings.json), adding value beyond 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?

Clearly states 'Get the platform-specific configuration JSON needed to install a single skill', with a specific verb (get/config) and resource (config JSON for a skill). Distinguishes from siblings by mentioning batch installs and packs.

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 says 'Use this when the user wants to install a specific skill...' and warns 'Do not use this for batch installs (use install_batch instead) or for packs (use install_pack instead)'. Also notes that the skill slug is automatically saved to agent memory.

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