pplx_smart_query

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

Given no annotations, the description carries full burden. It discloses quota checking, automatic model selection, and metadata output (model, routing reason, quota snapshot). The intent guide explains routing behavior. Does not mention rate limits or auth, but these are less critical for a query tool.

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?

Well-structured with front-loaded purpose and recommendation, then intent guide, then args. Every sentence adds value. Could be slightly shorter but remains clear and effective.

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 query tool with output schema, the description covers usage, intent selection, and parameter semantics adequately. Does not cover error cases or edge scenarios, but for the given complexity and sibling set, it is sufficiently complete.

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 0% (no descriptions in schema), but the description provides rich explanations: intent gets a full guide with examples, source_focus is described though briefly, and query is explained. This adds significant meaning beyond the bare schema.

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 it's a quota-aware query tool that auto-selects the best model, distinguishing it from many sibling query tools like pplx_ask, pplx_query, pplx_sonar, etc. The description positions it as the recommended default, providing specific verb+resource.

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 recommends 'USE THIS FOR EVERY QUERY unless the user explicitly requests a specific model.' Provides a detailed intent guide with specific use cases for each level. Lacks explicit when-not-to-use exclusions but context is clear.

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