pplx_list_threads

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

Discloses that the tool is free (zero quota cost), returns a paginated list, and lists the fields returned. While no annotations exist, the description covers key behavioral aspects without contradictions. Could have mentioned rate limits or error handling, but overall strong.

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?

Front-loaded with a clear one-liner, followed by structured sections (primary use cases, parameters). Every sentence adds value, no redundancy. Efficient and well-organized.

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 the tool's simplicity and the presence of an output schema, the description covers all necessary aspects: purpose, usage, parameters, and output fields. Explains how to use results (e.g., slug for pplx_get_thread), making it self-contained.

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?

Adds complete meaning for all three parameters (limit, offset, search_term) beyond the empty schema descriptions. Includes defaults, maximums, and practical usage context such as pagination and filtering. Fully compensates for 0% schema coverage.

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?

Clearly states the tool browses the Perplexity thread library, returns a paginated list with specific fields, and distinguishes from sibling tools like pplx_get_thread by providing use cases and alternative guidance.

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?

Explicitly lists primary use cases with examples: searching before spending a Pro query, finding a conversation to resume, and retrieving full history via pplx_get_thread. Provides explicit when-to-use and when-not-to-use scenarios.

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