open_list

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

With no annotations, the description carries the full burden and does meaningful work: assets are 'loaded and structurally checked before a TestClient session opens', missing assets yield 'open-list-navigation-unavailable with protocol_write_attempted=false', and 'A list-open has no business-data mutation or value read-back' signals a safe read-only operation. Gaps remain around session prerequisites (host/port/auth) and re-entrancy, but the failure contract and side-effect profile are unusually well 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 purpose is front-loaded and every paragraph touches real behavior, but the prose is dense with backtick-quoted internal tokens and stacked clauses ('the released, version-selected bundled bootstrap and value-read navigation templates') that slow parsing. It is not padded, but it is not cleanly tightened either.

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 six-parameter TestClient tool the description covers the key behavioral contract and, with an output schema present, is not obliged to spell out return values (though it gestures at them anyway). It still omits connection-parameter meaning and sibling routing, so it is adequate rather than 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 description coverage is 0%, so the description must compensate, and it only partially does: it clarifies capture (blank vs non-blank) and navigation_templates ('selects a controlled value-read template JSON'), and references base_link/target_link. It says nothing about host, port, or the catalog parameter, leaving three of six parameters undocumented anywhere.

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?

States a specific verb and resource ('Open a catalog/list window natively through e1cib/list/<path>'), so the core action is unambiguous and distinct from open_card or open_external_processor. However, it never explicitly contrasts itself with siblings like search_list or open_card, leaving the reader to infer the boundary from the resource name alone.

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?

It does explain two operating modes ('Omitting capture... uses the released, version-selected bundled bootstrap' vs 'A non-blank capture preserves the explicit capture-replay compatibility path'), which is genuine conditional guidance. But it never says when to reach for open_list versus alternatives such as open_card, search_list, or advanced_search, so the routing decision is left implicit.

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