Describe a solution

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

With no annotations, the description carries the full burden and does well: it discloses the export is unmanaged, that it runs asynchronously, that it unpacks locally, and that it is read-only against the environment. It stops short of naming auth prerequisites or rate/throughput limits, but the mutation and safety profile is substantively conveyed.

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?

It is a single dense sentence that front-loads the core action (export + unpack) before the inventory list, so the most important information appears first. It is information-rich rather than padded, though the component enumeration is long.

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?

There is no output schema, but the description compensates by enumerating the inventory contents an agent will receive (agents with harness/component counts, bot components by kind, flows, connection references, etc.). Combined with the async/read-only disclosure, this is nearly complete for the task.

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 name, workDir, and environment are already documented in the schema; the description adds no format, default, or validation detail beyond them. Baseline 3 applies when the schema does the heavy lifting.

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 gives a concrete verb sequence (export unmanaged + async, unpack locally, inventory contents) and enumerates the resource types produced (agents, bot components, cloud flows, connection references, environment variables, custom connectors). This clearly distinguishes the tool's inventory-oriented output from generic list tools, though it never names a specific sibling to contrast against.

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?

There is no explicit when-to-use guidance or exclusion relative to the many solution siblings (cs_list_solutions, cs_pull_solution, cs_pack_solution, cs_sync_solution). The only guidance-like line, 'Read-only for the environment,' describes a safety trait rather than a selection condition.

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