chat_perplexity

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It does reveal a key behavior: 'full history context' indicates that previous messages are maintained and used. However, it does not disclose other relevant behaviors such as potential errors with invalid chat_id, response format, latency, or any side effects. The description adds some value but remains minimal.

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 extremely concise, with two short sentences that effectively convey the tool's core functionality. It is front-loaded with the primary purpose and includes only essential additional context about chat continuation. No wasted 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?

For a low-complexity tool with two parameters, the description covers the main purpose but omits the return value or behavior details (e.g., what response is returned to the user). There is no output schema to compensate, and no annotations. The description is minimally viable but leaves some uncertainty about the tool's actual output.

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 100%, with both 'chat_id' and 'message' already documented in the schema. The description adds little beyond the schema, though it reinforces that chat_id is optional and controls chat creation/continuation. Since the schema already covers semantics, a baseline score of 3 is appropriate.

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 clearly states the tool's purpose: maintaining ongoing conversations with Perplexity AI, explicitly covering both new chat creation and continuation of existing ones with full history. It uses specific verbs (maintains, creates, continues) and identifies the resource (conversations with Perplexity AI), distinguishing it from sibling tools that perform search or documentation retrieval.

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 when a conversational interaction with Perplexity AI is needed, including creating a new chat or continuing an existing one. However, it does not explicitly compare with alternatives or state when not to use this tool (e.g., for simple search queries). The context is clear but lacks explicit exclusions.

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