ask_perplexity

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

Mentions that Sonar models have internet access and can perform searches, which is a behavioral trait. However, no annotations are provided, and the description does not disclose potential side effects, rate limits, or output format beyond what is implied.

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 concise, with bullet points and examples. Every sentence adds value. 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?

Given the tool's complexity (query tool), the description adequately covers usage, parameters, and model selection. The existence of an output schema means return values are handled externally. Minor gaps: no mention of required authentication or rate limits.

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%, so the description must compensate. It lists model options and their uses in the guidelines, but does not explain the 'prompt' parameter's semantics beyond being a prompt/question. The baseline is 3 with 2 parameters.

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 verb 'send a prompt to Perplexity' and the resource 'return the response'. It provides specific use cases (research, current events, comparisons) but does not directly differentiate from siblings like ask_perplexity_exact_response.

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 states when to use the tool (research, current events, comparisons) and when to use alternative models (reasoning for complex tasks, research by default). Provides examples of good prompts.

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