loaditout-mcp-server

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

No annotations provided, so description carries full burden. Discloses return structure ('JSON object with results array...and a not_found array') and cardinality limits ('Maximum 20'). Does not mention permission requirements or destructive nature of install operations, though 'not_found' array indicates partial failure handling.

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?

Five sentences, all earning place: purpose, return format, usage condition, exclusion/alternative, constraint. Front-loaded with action, no redundancy, efficient density of information.

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?

Comprehensive for a batch mutation tool without output schema: describes return structure, error handling (invalid slugs), distinguishes from sibling alternatives, and documents cardinality limits. No gaps given the complexity level.

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%, establishing baseline 3. Description adds minimum cardinality constraint ('2-20' vs schema's 'Maximum 20' only) and intent context ('you know all their slugs'), clarifying that slugs must be predetermined rather than discovered.

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?

Clear specific verb ('Install') with resource ('skills') and scope ('multiple specific'). Explicitly distinguishes from sibling install_pack by contrasting 'specific skills' vs 'curated collections'.

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?

Explicit when-to-use ('install 2-20 specific skills at once and you know all their slugs') and when-not-to-use with named alternative ('Do not use this for curated collections (use install_pack instead)'). Clear cardinality constraints.

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