Server Quality Checklist

Tool Scores

• symbol_occurrencesC
  2.9/5.0
  Behavior2/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 of behavioral disclosure. While it states what the tool does and the return type, it lacks critical behavioral details: whether it requires specific file permissions, what happens with invalid paths/line numbers, if it's read-only or has side effects, performance characteristics, or error handling. For a tool with no annotation coverage, this is a significant gap.

  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?

  The description is appropriately concise with three clear sections: purpose statement, args, and returns. Each sentence earns its place by providing essential information. The structure is front-loaded with the core purpose first. Minor improvement could be made by integrating the sections more fluidly, but overall it's efficient.

  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?

  Given the tool has an output schema (returns a dict), the description doesn't need to detail return values. However, with no annotations, 0% schema description coverage, and two parameters, the description should do more to explain behavioral aspects and usage context. It covers the basics but leaves gaps in error handling, permissions, and sibling differentiation, making it minimally adequate.

  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 description coverage is 0%, so the schema provides no parameter descriptions. The description adds basic semantics by explaining 'filePath' as 'Absolute path to the file' and 'lineNumber' as 'Line number in the file', which clarifies what each parameter represents. However, it doesn't provide format details, constraints, or examples (e.g., lineNumber starting at 0 or 1). This gives some value but doesn't fully compensate for the coverage gap.

  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 with a specific verb ('Get') and resource ('symbols occurring at a specific location in a file'). It distinguishes from siblings like 'get_occurrences' by specifying it's for symbols at a location rather than general occurrences, but doesn't fully differentiate from 'search_pattern' which might also involve file locations. The purpose is clear but sibling differentiation could be more explicit.

  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?

  The description provides no guidance on when to use this tool versus alternatives like 'get_occurrences' or 'search_pattern'. It doesn't mention prerequisites, constraints, or typical use cases. The agent must infer usage from the purpose alone, which is insufficient for optimal tool selection.

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

• get_occurrencesB
  3.2/5.0
  Behavior2/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 mentions that roles 'must be "reference" or "definition"' and returns a 'Dict containing all occurrences,' but lacks critical behavioral details such as whether this is a read-only operation, potential rate limits, error conditions, or how results are structured beyond 'Dict.' For a tool with no annotation coverage, this is insufficient.

  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 well-structured and front-loaded with the core purpose, followed by clear sections for Args and Returns. Every sentence adds value: the first states the tool's goal, the next two explain parameters, and the last specifies the return type. There's no wasted text.

  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?

  Given 2 parameters with 0% schema coverage and no annotations, the description does a decent job explaining parameters and the return type. However, it lacks context on behavioral aspects like safety, performance, or error handling. The presence of an output schema (implied by 'Has output schema: true') mitigates the need to detail return values, but overall completeness is only adequate.

  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?

  Schema description coverage is 0%, so the description must compensate. It effectively explains both parameters: 'usr' as 'The USR (Unified Symbol Resolution) of the symbol' and 'roles' as 'The roles to search for (must be "reference" or "definition").' This adds meaningful context beyond the bare schema, though it doesn't detail format constraints (e.g., USR string format) or array handling for roles.

  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: 'Get all occurrences of a symbol by its USR.' It specifies the verb ('Get'), resource ('occurrences of a symbol'), and key identifier ('USR'). However, it doesn't explicitly differentiate from sibling tools like 'symbol_occurrences' which likely has overlapping functionality, preventing a perfect score.

  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?

  The description provides no guidance on when to use this tool versus alternatives. With siblings like 'search_pattern' and 'symbol_occurrences' available, there's no indication of scenarios where this tool is preferred or should be avoided, leaving the agent to guess based on naming alone.

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

• load_indexB
  3.2/5.0
  Behavior2/5

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

  With no annotations provided, the description carries full burden for behavioral disclosure. It mentions loading from 'Derived Data folder' and returns a success boolean, but fails to describe critical traits like whether this is a read-only operation, if it requires specific permissions, potential side effects (e.g., caching), or error conditions. This leaves significant gaps for a tool that interacts with project data.

  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 efficiently structured with a clear purpose statement followed by Args and Returns sections. Every sentence earns its place by providing essential information without redundancy, making it easy to parse and front-loaded with the core function.

  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?

  Given the tool's moderate complexity (1 parameter, no annotations, but with an output schema), the description is minimally adequate. The output schema covers the return value, so the description doesn't need to explain returns further. However, it lacks details on behavioral aspects and usage context, leaving room for improvement in guiding the agent effectively.

  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 description adds meaningful context beyond the input schema, which has 0% description coverage. It explains that 'projectName' refers to 'Name of the project to load the index for', clarifying the parameter's purpose. However, it doesn't detail format constraints (e.g., case sensitivity) or examples, keeping it from a perfect score.

  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 action ('Load the IndexStore') and resource ('for a project from the Derived Data folder'), providing specific verb+resource pairing. However, it doesn't explicitly differentiate from sibling tools like 'get_occurrences' or 'search_pattern', which likely operate on different resources or with different purposes.

  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?

  No guidance is provided on when to use this tool versus alternatives. The description lacks context about prerequisites (e.g., whether the project must exist or be indexed first) or exclusions, leaving the agent with no usage boundaries beyond the basic function.

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

• search_patternB
  3.4/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 that the tool searches for symbol occurrences and returns a dict with canonical symbols, which gives basic behavioral context. However, it lacks details on permissions, rate limits, side effects, or error handling. For a search tool with no annotations, this is minimal but not entirely absent.

  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?

  The description is well-structured with clear sections for Args and Returns, using bullet points for options. It's front-loaded with the core purpose and avoids unnecessary fluff. However, the formatting could be slightly more compact, and some sentences are a bit 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 moderate complexity (2 parameters, no annotations, but with an output schema), the description is reasonably complete. It explains the purpose, parameters, and return value. The output schema exists, so the description doesn't need to detail return values further. It covers the essentials but could benefit from more behavioral context.

  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?

  Schema description coverage is 0%, so the description must compensate. It adds significant value by explaining 'pattern' as the search pattern and detailing 'options' with valid values like 'anchorStart', 'anchorEnd', etc., including their semantics. This goes beyond the schema's basic types, though it doesn't cover all parameter nuances like format constraints.

  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 verb 'search' and resource 'symbol occurrences matching a pattern', which is specific and actionable. However, it doesn't explicitly differentiate from sibling tools like 'get_occurrences' or 'symbol_occurrences', which likely have overlapping functionality. The purpose is clear but lacks sibling differentiation.

  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?

  The description provides no guidance on when to use this tool versus alternatives like 'get_occurrences' or 'symbol_occurrences'. It mentions what the tool does but offers no context about use cases, prerequisites, or exclusions. This leaves the agent without direction on tool selection.

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