Server Quality Checklist

Tool Scores

• find_company_pageA
  4.4/5.0
  Behavior5/5

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

  Annotations already declare readOnly/openWorld/idempotent, and the description builds substantially on them: discovery method order, 'guessing a URL path is the LAST method tried and is scored 0.6 or below,' found=false vs null semantics, browser never used against blocks/CAPTCHAs, one row per input, APIFY_TOKEN and credit consumption. This is exemplary behavioral disclosure.

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

  Conciseness5/5

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

  The description is long but information-dense and front-loaded. The opening sentence states core behavior, and every subsequent sentence adds load-bearing operational detail: available page types, discovery heuristics, confidence thresholds, output semantics, costs, and auth. No wasted words.

  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?

  Given the tool's complexity (14 params, no output schema), the description covers the key behavioral context: return values (URL, method, confidence), interpretations of found=false/null, coverage/fetch_status, and what locate_and_extract adds. It doesn't enumerate all response fields, but it describes the critical ones sufficiently.

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

  Parameters3/5

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

  Schema coverage is 100% with all 14 parameters documented, so baseline is 3. The description adds contextual meaning (mode costs extra events, companies path runs identity resolution, knownUrls skips discovery) but does not need to re-explain parameter syntax since the schema already does that thoroughly.

  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?

  The first sentence is a specific verb+resource: 'Give it a company domain and name a page type. It finds that page on the company's own website and returns the URL, the method, and a confidence.' This unambiguously states what the tool does and distinguishes it from generic web search even without sibling tools.

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

  Usage Guidelines4/5

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

  The description provides clear context: when to use locate vs locate_and_extract, 'Use domains instead whenever you hold a domain,' 'ask for what you will use' for pageTypes, and knownUrls to skip discovery. No explicit exclusions or alternatives are needed since there are no sibling tools, but the guidance is strong.

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