Server Quality Checklist

Tool Scores

• search_jobsA
  4/5.0
  Behavior4/5

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

  With no annotations, the description carries the full burden and does a good job: it discloses billing per row, max_jobs as a hard spend cap, filter-before-billing semantics, and that data is fetched live from ATS APIs. It does not mention failure modes for invalid companies or rate limits, but the key operational trait—cost—is transparent.

  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?

  Four sentences, all earning their place: the core operation is front-loaded, followed by identifier format, cost behavior, and spend-cap warning. There is no filler or repetition of schema fields.

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

  Completeness3/5

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

  Output schema covers return values, so that omission is fine. The definition is strong on cost and company-identifier format, but because two parameters are undocumented in both the schema and description, and list_supported_ats is never referenced, the agent cannot fully plan all call variants.

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

  Parameters2/5

  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 explains companies (provider:slug or career-site URL) and max_jobs (spend cap), but remote_only and title_contains are left completely unexplained, leaving the agent unable to know their exact behavior from the definition.

  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 opening sentence identifies a specific action (fetch live job postings) and a concrete resource (named companies' ATS board APIs). The provider:slug/URL detail and 'use resolve_company first' clearly differentiate it from its 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?

  Explicitly instructs to call resolve_company first when only a name is available, and explains that narrow queries are cheaper because filters are applied before billing. However, no guidance covers when to use list_supported_ats or when search_jobs would not be the right tool.

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

• list_supported_atsA
  4.5/5.0
  Behavior4/5

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

  With no annotations provided, the description carries the burden of behavioral disclosure. It usefully states 'No network, no cost,' signaling that this is a safe, local, read-only introspection call. It does not fully enumerate all behavioral details, but for a zero-parameter list operation this is strong 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?

  A single sentence communicates the resource, the purpose, the relationship to a sibling tool, and the operational characteristics ('No network, no cost'). There is no redundancy or filler.

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

  Completeness5/5

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

  For a simple, zero-parameter introspection tool with an output schema, the description is complete. It tells the agent what the tool does, what it returns, how the result is used by search_jobs, and that it has no side effects. Nothing essential is missing.

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

  Parameters4/5

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

  There are zero parameters, so parameter-semantics burden is minimal. The schema coverage is effectively 100%, and the description adds relevant context about what the returned provider slugs mean and how they relate to search_jobs.

  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 description identifies a specific verb ('List'), a specific resource ('applicant-tracking systems this server can read'), and the useful detail that it exposes the 'provider:slug' form expected by search_jobs. This clearly distinguishes it from sibling tools like search_jobs and resolve_company.

  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 clearly implies when to use this tool: before calling search_jobs, to learn which ATS providers are supported and what slug format to provide. It does not explicitly state when not to use it, but the context is clear and the sibling distinction is strong.

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

• resolve_companyA
  4.6/5.0
  Behavior4/5

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

  With no annotations provided, the description carries the full burden of behavioral disclosure. It does well: it names the data source (public CC-BY ats-directory), explains that URLs are read directly while names are matched, notes that every match is returned, defines status values, and clarifies there is no Apify run or billing. Minor gaps like no-match behavior are not covered, but the key behavioral traits are disclosed.

  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 four sentences, each earning its place: purpose, input-type handling, output/status semantics, and cost. It is front-loaded with the core purpose and contains no filler.

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

  Completeness5/5

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

  Given a single parameter, an output schema that can document return structure, and no annotations, the description provides sufficient context: what the tool does, how the input is interpreted, what matches include, and that it is free. Nothing essential for selecting or invoking the tool correctly is missing.

  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?

  The input schema only defines 'url_or_name' as a string with 0% schema description coverage, so the description must compensate. It does so thoroughly by specifying both accepted forms (company name or career-site URL) and how each is processed. This adds real meaning beyond the bare schema.

  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 description uses a specific verb ('Map') and a resource ('company name or career-site URL') to produce a clearly defined output ('provider:slug' pair). It also explicitly ties this to search_jobs, making the tool's role distinct from its siblings without needing to open schemas.

  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 clearly implies when to use this tool: before calling search_jobs, since it produces the pair search_jobs consumes. It also clarifies behavior for the two supported input types (URL vs. name). It does not explicitly state exclusions or compare against list_supported_ats, but the context is clear enough.

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