DollhouseMCP

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

With no annotations provided, the description carries the full burden of behavioral disclosure. While 'configure' implies a mutation/write operation, the description doesn't specify whether this requires authentication, what permissions are needed, whether changes are immediate or require a restart, or what happens if configuration fails. For a mutation tool with zero annotation coverage, this is a significant gap in behavioral transparency.

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 a single, efficient sentence that directly states the tool's purpose. It's appropriately sized and front-loaded with the core function. While it could potentially be more structured with separate usage guidance, every word contributes meaning without unnecessary elaboration.

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 configuration/mutation tool with no annotations and no output schema, the description is insufficiently complete. It doesn't address important contextual aspects like authentication requirements, error conditions, whether configuration persists across sessions, or what the tool returns (success/failure indicators). The user must guess these critical behavioral aspects.

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 already fully documents all four parameters. The description lists the types of settings (auto-sync preferences, default visibility, submission settings, repository preferences) which loosely maps to the parameters, but adds no additional semantic meaning beyond what's in the schema. This meets the baseline expectation when schema coverage is complete.

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 tool configures portfolio settings with specific examples (auto-sync preferences, default visibility, submission settings, repository preferences). It uses the verb 'configure' with the resource 'portfolio settings', making the purpose unambiguous. However, it doesn't explicitly differentiate from sibling tools like 'dollhouse_config' or 'portfolio_status'.

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 no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites (like needing an initialized portfolio), when configuration is appropriate, or how this differs from other portfolio-related tools like 'init_portfolio', 'portfolio_status', or 'sync_portfolio'. The user must infer usage context from the tool name alone.

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