Server Quality Checklist

Tool Scores

• ask_perplexityA
  4.6/5.0
  Behavior4/5

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

  No annotations provided, so description carries full burden. It explains that Perplexity is an LLM that searches, opens results, finds info, and answers. Details query types and file attachment behavior. Lacks mention of potential inaccuracies or response format, but overall sufficiently transparent.

  Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

  Conciseness4/5

  Is the description appropriately sized, front-loaded, and free of redundancy?

  Description is lengthy but well-structured with sections, examples, and bullet points. Front-loaded with core purpose. Could be slightly more concise, but each section serves a purpose in guiding usage.

  Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

  Completeness4/5

  Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

  Covers main use cases, query types, file attachments, language requirement, and prompt engineering. No output schema, but output is implied to be an answer. Adequate for an LLM-based search tool.

  Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

  Parameters5/5

  Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

  Schema coverage is 100%, but description adds significant value: explains the 'simple' vs 'complex' enum with cost/speed implications, and clarifies that 'attachment_paths' must be absolute paths. Provides context for 'query' via examples.

  Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

  Purpose5/5

  Does the description clearly state what the tool does and how it differs from similar tools?

  Description clearly states that Perplexity searches the internet and answers queries, with explicit differentiation between simple and complex queries. The verb 'ask' and resource 'perplexity' are well-defined, and no sibling tools exist to cause confusion.

  Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

  Usage Guidelines5/5

  Does the description explain when to use this tool, when not to, or what alternatives exist?

  Provides explicit guidance on when to use simple vs complex queries, including cost and speed trade-offs. Includes instructions to use the tool for uncertain queries and emphasizes English-only queries. Offers prompt engineering tips and absolute path requirements for attachments.

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