Describe a solution

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

With no annotations, the description carries the burden of behavioral disclosure. It clearly states the operation is an unmanaged async export, unpacking happens locally, and the environment remains read-only. It does not detail async result retrieval or output format, but the core side effects and safety profile 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 a single efficient sentence that front-loads the core action and then lists the inventory categories compactly. Every phrase earns its place without redundancy.

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 tool's purpose, local side effects, environment safety, and the expected inventory contents, which is sufficient for an agent to decide to call it. The main gap is the lack of an explicit output/return format, especially given the async nature, but the inventory list provides a strong signal of what to expect.

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 all three parameters are already documented. The description adds useful operational context (unmanaged, async, local unpack) but does not need to restate parameter semantics; it provides no additional per-parameter detail.

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 states specific actions (export, unpack, inventory) and the resource (a solution). It also enumerates exactly what is inventoried, making it easy to distinguish from sibling tools like cs_check_solution or cs_pack_solution.

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 the tool is for inspecting a solution's contents without modifying the environment, and the 'Read-only for the environment' note gives a clear safety cue. However, it does not explicitly contrast it with alternatives such as cs_check_solution or cs_describe_connector, or state when not to use it.

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