Import a solution zip

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

With no annotations, the description discloses that the tool mutates the environment and requires confirm:true, which is valuable. However, it doesn't mention the dry-run behavior when confirm is false, the effects of forceOverwrite, or any permission requirements—leaving gaps that the agent must infer.

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 and then states the key behavioral constraint. No wasted words, and it is easily scannable.

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 tool with 5 parameters, no output schema, and no annotations, this description is incomplete. It omits explanations for most parameters, the dry-run behavior, and any success/failure indicators, leaving the agent with insufficient guidance for correct invocation.

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 only 20% (only confirm has a description). The description adds semantic context for confirm (requires true for mutation) and environment (implicitly the target), but doesn't explain path, forceOverwrite, or publishChanges. Given the low coverage, it fails to compensate sufficiently.

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 identifies the tool's purpose: importing a packed agent solution into an environment, referencing the source (cs_pack) and the mutation aspect. It distinguishes from siblings like cs_pack_solution (packing) and cs_check_solution (checking) by naming the import action, though it doesn't explicitly contrast with all import-like tools.

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 implies usage as the counterpart to cs_pack (imports what was packed) and notes the confirm:true requirement for mutation. It lacks explicit when-not-to-use guidance or mention of alternatives like cs_deploy_solution or cs_pull_solution, but does provide a condition for actual change.

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