Server Quality Checklist

Tool Scores

• channel_lensB
  3.4/5.0
  Behavior3/5

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

  With no annotations, the description carries the burden of disclosure. It describes the output content and notes that partial matches are accepted, revealing relevant behavior. However, it does not state whether the operation is read-only, what happens on no match, or any side effects, leaving meaningful gaps for a tool with no annotation support.

  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 a compact two-sentence statement with no redundancy. It front-loads the core purpose ('Inverse view for one channel') and efficiently lists the analytical dimensions, making every word informative.

  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?

  For a simple one-parameter tool, the description covers its primary function and input characteristics. However, it lacks explicit usage context relative to sibling tools, does not describe the output format or edge cases, and does not clarify what 'inverse' means operationally. Given the absence of an output schema and annotations, these omissions leave noticeable gaps.

  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?

  The schema provides only a required string 'channel' with no description. The description adds significant semantic value by specifying that a partial channel name is acceptable, which informs how the parameter should be used. This compensates for the 0% schema description coverage.

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

  Purpose4/5

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

  The description clearly states the tool's purpose as an 'inverse view' for a channel, specifying the output dimensions (commonness, stage split, sector usage, companies). It conveys a specific verb and resource, and the 'inverse' framing hints at a different perspective from sibling tools, though it does not explicitly name alternatives.

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

  Usage Guidelines2/5

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

  There is no explicit guidance on when to use this tool versus alternatives like find_channels or search_evidence. The phrase 'inverse view' implies a distinct use case, but it does not state any exclusions or comparative advantages, leaving the agent without clear decision criteria.

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

• get_companyA
  3.7/5.0
  Behavior3/5

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

  With no annotations, the description carries the burden. It discloses fuzzy matching and the return contents, but does not mention read-only/no side effects, failure behavior, or data freshness. Adequate but not rich.

  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?

  One tightly packed sentence, front-loaded with the core purpose, followed by a clear colon-separated list of returned data. No filler or redundancy.

  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?

  For a one-parameter lookup without an output schema, the description covers the matching behavior, scope, and return categories. It lacks guidance on alternatives but otherwise is complete enough to invoke correctly.

  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?

  The single parameter 'name' gains meaning from the description: it identifies a company and uses fuzzy matching. This exceeds the bare schema, which only provides the type and title.

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

  Purpose4/5

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

  The description clearly states it returns a full channel profile for one company, enumerating contents. It distinguishes from siblings by focusing on a single company with fuzzy name match, though it lacks an explicit verb like 'retrieve'.

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

  Usage Guidelines3/5

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

  Usage is implied: use this when you need a comprehensive profile for one company. There is no explicit comparison with siblings like find_channels or dataset_summary, nor a statement of when not to use it.

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

• search_evidenceA
  3.8/5.0
  Behavior3/5

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

  No annotations are provided, so the description carries the full burden. It discloses the output behavior (returns short snippets with company names) and the scope of evidence searched. However, it does not explicitly state that the operation is read-only, nor does it mention rate limits, pagination, or side effects. For a search tool, the transparency is adequate but incomplete.

  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 exactly two sentences, front-loaded with the primary action, and contains no extraneous information. It includes usage examples and output format without editorializing, making it concise and well-structured.

  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?

  The description explains the return value (short snippets with company names) despite lacking an output schema. It also gives a sense of the evidence scope. However, missing parameter details and lack of annotations leave gaps for a tool with no output schema and sparse input schema, so it is only partially complete.

  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%, and the description does not compensate. It implies query_text is the search term but does not explain the limit parameter or its default behavior. There is no parameter-specific guidance beyond the broad notion of 'keyword search'.

  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 clearly states the tool performs a keyword search across narrative evidence, listing specific content areas (what worked/failed, signature moves, ignition). It also clarifies the return format (short snippets with company names, not full rows), which distinguishes it from tools like get_company that return full rows.

  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 specific example use cases ('when did X fail', 'who used Y for Z'), giving clear context for when to use the tool. However, it does not mention when not to use it or explicitly compare to sibling tools, so it lacks exclusions or alternatives.

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

• dataset_summaryA
  4.3/5.0
  Behavior3/5

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

  No annotations are provided, so the description carries the burden. It implies a read-only, low-cost operation with the words 'Orientation' and 'Cheap', but doesn't explicitly state side effects, return format, or other behavioral details.

  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 two sentences, front-loaded with the purpose ('Orientation call') followed by specifics and usage guidance. Every word earns its place with no redundancy.

  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 zero-parameter tool, this description fully covers what the tool does and when to use it. It gives enough detail on the output (counts by categories) and the practical context (cheap, first step), making it complete for its simplicity.

  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?

  The tool accepts zero parameters, and the empty schema is fully described. There is no parameter semantics burden, and the baseline for no params is 4.

  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 clearly states the tool's function: it provides counts of companies split by status, era, confidence, and sector. This distinguishes it from sibling tools like get_company or search_evidence.

  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 'Use this first' for orientation before querying, providing clear context for when to invoke it. However, it doesn't mention specific alternatives or when not to use it, so it falls short of a full 5.

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

• find_channelsA
  4.4/5.0
  Behavior4/5

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

  Since no annotations are provided, the description carries the full burden of behavioral disclosure. It reveals important behavioral traits: results are ranked by prevalence and split by growth stage, and a cohort_size field is returned with possible warnings that should be honored. It does not disclose return format in full (e.g., exact JSON structure) or any side effects, but for a read-only-style tool this is sufficient. The explicit warning handling instruction adds meaningful transparency beyond just 'returns channels.'

  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 concise yet comprehensive, using three short paragraphs with clear structure. It front-loads the tool's primary purpose and then details parameters and output handling in an organized manner. Every sentence adds value, with no filler or repetition of schema information. It is long enough to be useful but not verbose.

  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 (10 parameters, no output schema), the description covers the essential aspects: purpose, input parameters with allowed values, and output expectations (cohort_size, warnings). It does not specify the full response format or how to interpret all fields, but the named example companies and stage split are mentioned. A minor gap is the lack of an example invocation, but the description is largely complete for an agent to invoke it correctly.

  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?

  The schema has zero description coverage for all 10 parameters, so the description must compensate. It provides semantic meaning for most parameters: sector (group/raw), business_model (list of values), era (specific ranges), trust_burden, virality, cac_ceiling, category_play (with enums), and explains the 'stage' parameter's role in ranking. However, it leaves 'status' and 'top' without explanation, but 'top' is intuitive (default 12) and 'status' may be self-evident. Overall, strong compensation for the missing schema descriptions.

  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 clearly identifies the tool as 'PRIMARY TOOL' and states its specific function: return channels used by comparable Indian startups, ranked by prevalence and split by growth stage. It distinguishes itself from sibling tools by emphasis on 'used by comparable Indian startups' and the ranking/splitting behavior, which is unique and not mentioned in sibling names. The verb 'return' is precise.

  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 usage context: 'Given a marketing situation' and explicitly lists the subset of parameters that can be passed, which guides when to use the tool. It also instructs to 'Always report the returned cohort_size and honor any warning,' which is a usage requirement. However, it does not explicitly mention alternatives or when not to use this tool, unlike a tool that says 'use X instead.'

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

• list_filtersA
  4.5/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. It discloses that the tool returns valid values for all filters accepted by find_channels and lists the categories, which gives a clear behavioral profile. It does not describe the return format, but for a simple parameterless list tool this is a minor gap.

  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 two sentences, front-loads the core purpose, and includes only necessary detail. Every word earns its place, and the parenthetical enumeration adds valuable specificity without bloat.

  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 parameterless, output-schema-less tool with sibling context, the description is complete: it identifies the data returned, the associated tool (find_channels), and provides usage guidance. No critical information 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?

  The tool has zero parameters and schema coverage is 100%, so the baseline is 4. The description adds meaningful context by explaining what the output represents (valid filter values for find_channels), even though there are no parameters to document.

  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 ('Return') and resource ('valid values for every filter accepted by find_channels'), clearly distinguishing it from sibling tools. It also enumerates the filter categories (sector groups, business models, eras, statuses, etc.), making the tool's scope unambiguous.

  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 phrase 'Call this if unsure what to pass' provides explicit when-to-use guidance, especially relative to find_channels. However, it does not mention when not to use or describe alternatives, so it falls just short of full marks.

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