recent_threads

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

With no annotations, the description adds some behavioral context (returns thread summaries, threadId, newest first), but does not disclose safety, authentication, or pagination behavior. It prevents contradictions but lacks depth.

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?

Two sentences efficiently front-load the core action and filters, followed by use case and output hint. No redundant words.

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?

Given 5 parameters and no output schema, the description mentions only two filter types (source, project) and omits 'starred', 'tags', 'limit' details. It partially explains output but misses covering all options.

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 coverage is 100%, so the description adds minimal value beyond paraphrasing 'source or project path' filters. It does not introduce new meaning for parameters like 'starred' or 'tags'.

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 clearly states 'List the user's most recently updated conversation threads (newest first)' with specific verb and resource, and distinguishes from sibling tools like 'search_threads' by focusing on recency rather than search.

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 provides usage context ('Use this to see what the user has been working on lately') and mentions optional filtering, but does not explicitly state when not to use this tool or compare to alternatives like 'search_threads'.

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