list_conversations

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

With no annotations, the description carries the full burden and does add one important behavioral limitation: 'Transcripts are not stored locally,' which usefully prevents callers from expecting full chat history. However, it does not disclose whether the operation is read-only, how 'recent' is defined, or how results are ordered/paginated.

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 description is a single, front-loaded sentence with no filler. It names the action and resource, lists key returned fields, and appends a meaningful limitation in a compact way.

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 and no annotations, so the description must carry more weight. It covers the main returned fields and one key limitation, but omits parameter semantics (especially limit and query) and any detail about ordering, paging, or result format. Adequate for a simple list tool, but with clear gaps.

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 low at 33%, with only working_directory documented in the schema. The tool description adds no parameter-level meaning: limit and query are not explained, and the text focuses only on the output shape rather than how the parameters affect the result set.

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 states a specific verb ('List'), a clear resource ('Warp agent conversations'), and a scope ('recent'), while enumerating what is returned: title, first prompt, and linked plans. It is clearly distinct from sibling list tools like list_memories and list_notebooks, though it does not explicitly contrast with get_conversation.

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 guidance is given about when to use this tool versus alternatives such as get_conversation or search. The word 'recent' implies recent-only scope, but there is no explicit when-not-to-use condition or pointer to sibling tools for full-detail retrieval.

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