portfolio_config

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 write/mutation operation, the description doesn't specify whether this requires authentication, what permissions are needed, whether changes are reversible, or what happens when configuration is applied. It also doesn't mention side effects, error conditions, or response format.

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 front-loads the core purpose. It avoids unnecessary words while covering the main configuration areas. However, it could be slightly more structured by separating the different setting types more clearly.

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 tool with 4 parameters and 100% schema coverage but no annotations or output schema, the description provides adequate basic information about what can be configured. However, it lacks important context about behavioral aspects (permissions, side effects, error handling) that would be crucial for safe and effective use of a configuration mutation tool.

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?

The description lists the four configuration areas (auto-sync preferences, default visibility, submission settings, repository preferences) which map directly to the four parameters in the schema. Since schema description coverage is 100%, the schema already provides complete parameter documentation. The description adds minimal value beyond what's in the schema, meeting the baseline expectation.

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's purpose as configuring portfolio settings with specific examples (auto-sync preferences, default visibility, submission settings, repository preferences). It uses the verb 'configure' with the resource 'portfolio settings' but doesn't explicitly differentiate from sibling tools like 'dollhouse_config' or 'portfolio_element_manager' which might handle different aspects of portfolio management.

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, timing considerations, or relationships to sibling tools like 'init_portfolio' (which might be for initial setup) or 'sync_portfolio' (which might handle synchronization operations). 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.