co_list_documents

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, covering the safety profile. The description adds useful context about scope (only open documents) and frontmost state, but does not explain return shape or how 'frontmost' is represented.

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?

A single concise sentence that front-loads the main verb 'List' and includes only necessary scope information. No filler or 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?

For a zero-parameter, read-only list tool with safety annotations, the description is sufficient for correct invocation. It tells the agent exactly what the tool returns—open sessions and catalogs plus the frontmost one—and no arguments are needed.

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?

The tool has zero parameters and the schema is complete at 100% coverage, so the description carries no parameter burden. Baseline 4 applies.

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: lists currently open Capture One sessions/catalogs and identifies which is frontmost. This clearly differentiates it from sibling list tools like co_list_collections and co_list_variants, which enumerate different object types.

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 phrasing 'currently open' and 'frontmost' gives clear context for when to call this tool, such as discovering available documents or determining the active one. It does not explicitly name alternatives or exclusion conditions, but the use case is self-evident for a zero-parameter list tool.

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