pplx_ask

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

No annotations provided, so description must cover behavioral traits. It mentions cost (1 Pro search query) and 'auto model', but does not explain auto model selection, output format, rate limits, or error behavior. Adequate for a simple tool 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 concise sentences, front-loaded with purpose. Efficient but could be slightly more structured to include parameter hints or output details without becoming verbose.

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?

With 3 parameters, no parameter docs, and an output schema not referenced, description is incomplete. It covers cost and usage guidance but lacks essential parameter and output explanations needed for effective use.

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 0%, but description adds no parameter info. Does not explain 'query', 'source_focus', or 'conversation_id'. Fails to compensate for the schema gap.

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 'Quick Q&A with auto model', giving a specific verb (ask) and resource (Query & Answer). It also specifies cost (1 Pro search query) and differentiates from sibling pplx_smart_query by directing to use that for simple lookups with Sonar 2 first.

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 says 'Prefer pplx_smart_query(intent='quick') for simple lookups (Sonar 2 first)', providing clear when-to-use and alternative. Also implies this tool is for quick Q&A, giving context for its use.

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