chat_list

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

With no annotations, the description carries the behavioral burden, and it does so adequately: 'List persisted...' clearly implies a read-only operation, and the parenthetical names the exact fields returned. It does not discuss ordering, pagination, or user scoping, but for a zero-parameter read-only list 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 front-loaded sentence that names the action, resource, and output fields with no filler. It is concise without being a tautology and every clause earns its place.

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 parameterless list tool with no output schema, mentioning the returned fields is sufficient for basic invocation. It could add ordering or clarify whether 'GUI/MCP' means two separate thread sources, but nothing critical is missing.

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?

There are no parameters, so there is no missing parameter documentation to compensate for. The schema is fully covered by virtue of having an empty properties object, and the description adds no conflicting or misleading input semantics.

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 — 'List persisted GUI/MCP chat threads' — and enumerates the returned fields (id, title, agents, updatedAt). The resource is distinct from sibling tools like list_agents and list_runs, so an agent can tell it apart without opening a schema.

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?

No when-to-use guidance, exclusions, or references to alternatives are provided. The description does not help an agent decide between chat_list and related listing tools such as list_agents, list_runs, or list_local_models.

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