manage_config

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

With no annotations, the description must convey side effects. It does mention that migrate moves files, export zips, import restores (with backup), and use writes a .podcli-marker. This covers key mutations. It does not mention permissions, return values, or error handling, but the core behavioral effects are disclosed.

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 well-structured with a brief lead-in and a bulleted list of actions. Each action has a short, informative description. There is no redundant or extraneous content; it is efficient and focused.

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?

The description covers the main behaviors and effects of each action, making it fairly complete for a configuration management tool. However, it does not describe expected return values or output formats (since there is no output schema), nor does it mention potential error states or edge cases. These omissions are not critical but keep it from being fully complete.

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 80% with each parameter having a description (home, action, dry_run, activate, bundle_path). The tool description adds little beyond these schema descriptions—it restates action names but does not elaborate on parameter nuances or relationships. Since coverage is high, the baseline is 3, and no additional semantic depth is provided.

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: managing portable config profiles and legacy path migration. It lists five specific actions (status, migrate, export, import, use) with brief explanations, distinguishing it from the sibling tools which handle transcription, clips, assets, and other unrelated concerns.

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 implicitly indicates when to use the tool (for config management, migration, export/import, activation) but does not explicitly contrast with alternatives or provide 'when-not-to-use' guidance. The actions are self-explanatory enough for an agent to infer appropriate usage, but explicit conditions are absent.

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