install_collection_content

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

With no annotations provided, the description carries the full burden. It discloses the tool's purpose (installation from collection to portfolio) and element types, but lacks details on behavioral traits like whether installation overwrites existing elements, requires authentication, has rate limits, or what happens on success/failure. It provides basic context but misses operational specifics needed for a mutation tool.

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 efficiently structured: first sentence states the purpose, second provides usage guidelines with examples. Every sentence adds value—no redundancy or fluff. It's front-loaded with the core action and appropriately sized for a single-parameter tool.

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?

For a mutation tool with no annotations and no output schema, the description adequately covers purpose and usage but lacks completeness in behavioral context (e.g., side effects, error handling) and output details. It compensates somewhat with examples, but given the tool's complexity (installing elements), more operational transparency would be beneficial.

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 fully documents the 'path' parameter's format and example. The description adds no parameter-specific semantics beyond implying the path corresponds to element types (personas, skills, etc.), which is already covered in the schema's description. This meets the baseline for high schema coverage.

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 clearly states the specific action ('Install AI customization elements FROM the DollhouseMCP collection TO your local portfolio') and resource ('personas, skills, templates, agents, or memories'), distinguishing it from siblings like 'browse_collection' or 'get_collection_content' which don't involve installation. It explicitly identifies the source (collection) and destination (portfolio) with a directional flow.

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 provides explicit usage guidance: 'Use this when users ask to download/install any element type... from the collection' and lists concrete examples (e.g., 'install the creative writer persona'). It clearly distinguishes this from alternatives like 'browse_collection' (for exploration) or 'get_collection_content' (for viewing without installation).

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