list_output_items

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

No annotations are provided, so the description carries the burden. It discloses that this lists output value configurations for the current session, which is the core behavior. However, it does not describe the output format, whether all configuration fields are returned, or ordering — though for a simple listing tool this is a minor gap.

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, compact sentence with zero waste. The resource and scope are declared immediately and nothing extraneous is included. Ideal conciseness for a simple list tool.

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 listing tool with no output schema, the description fully covers what an agent needs: what it lists and the session scope. No missing information would prevent 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?

The tool has zero parameters and schema coverage is trivially 100%, so there is nothing for the description to explain. Per the baseline rule for 0-parameter tools, the description need not add parameter detail. It correctly matches the empty schema.

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?

Description states a specific verb ('列出' - list) and resource ('输出值配置' - output value configurations) scoped to the current session. The phrase '当前会话中' adds scope clarity that distinguishes it from sibling tools like add_output_item, remove_output_item, and update_output_item.

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 a read/query operation for retrieving output configurations, and the 'current session' scope provides some context. However, it does not explicitly state when to prefer it over alternatives, nor does it mention that it complements the related add/remove/update_output_item tools. Usage is implied but not explicit.

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