Server Quality Checklist

Tool Scores

• buildC
  2.9/5.0
  Behavior2/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 states the tool builds an Xcode project but doesn't describe what happens during execution (e.g., whether it shows build output, returns success/failure, handles errors, or requires specific permissions). For a build tool with potential side effects, this lack of behavioral context 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.

  Conciseness5/5

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

  The description is extremely concise—just two sentences that directly state the purpose and key parameters. Every word earns its place with no redundancy or fluff. It's front-loaded with the core action and efficiently lists relevant parameters without unnecessary elaboration.

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

  Completeness2/5

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

  For a build tool with 6 parameters, no annotations, and no output schema, the description is insufficient. It doesn't explain what the tool returns (build logs, success status, artifacts), error handling, or execution context. Given the complexity of building Xcode projects and the lack of structured metadata, the description should provide more complete operational context.

  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 100%, so the schema already documents all 6 parameters thoroughly. The description adds minimal value by listing some parameter names (target, scheme, configuration, destination) but doesn't provide additional semantics beyond what's in the schema. This meets the baseline for high schema 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 action ('Build an Xcode project using xcodebuild') and specifies the resource (Xcode project). It distinguishes from siblings like list-projects or read-project by focusing on building rather than listing or reading. However, it doesn't explicitly differentiate from potential build-related siblings that might exist in other contexts.

  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. While it mentions parameters like target, scheme, configuration, and destination, it doesn't indicate when to choose this tool over other build tools or how it relates to the listed sibling tools (list-projects, list-schemes, etc.). There's no mention of prerequisites, dependencies, or typical workflow context.

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

• list-targetsB
  3.1/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 full burden. It states the tool lists targets with product types, but doesn't disclose behavioral traits such as whether it requires specific permissions, how it handles invalid project paths, if it's read-only, or what the output format looks like (e.g., JSON, list). This leaves significant gaps for a tool with no annotations.

  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 single, efficient sentence that directly states the tool's purpose without waste. It's appropriately sized and front-loaded, with every word contributing to clarity.

  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 no annotations, no output schema, and a simple input schema, the description is minimally adequate. It covers the basic purpose but lacks details on behavior, output, or usage context. For a tool with no structured data beyond the schema, it should do more to compensate, but it meets the bare minimum.

  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 100%, with the parameter 'projectPath' documented in the schema. The description doesn't add any meaning beyond what the schema provides (e.g., no extra details on path format or examples). Baseline is 3 since the schema does the heavy lifting.

  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 ('List') and resource ('build targets in an Xcode project') with specific attributes ('with their product types'). It distinguishes from siblings like 'list-projects' and 'list-schemes' by focusing on targets, but doesn't explicitly differentiate from 'read-project' which might also provide target information.

  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 like 'read-project' or 'list-schemes'. The description implies usage for listing targets, but lacks explicit context, exclusions, or comparisons with sibling tools.

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

• read-projectB
  3.1/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 states the tool reads and parses a file, implying a read-only operation, but doesn't clarify permissions needed, error handling (e.g., for invalid paths), performance characteristics, or format of the returned structure. While it mentions the return content, it lacks details on depth, pagination, or data format, leaving behavioral gaps.

  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 highly concise and well-structured in two sentences: the first states the action and resource, the second specifies the return value. Every word earns its place with no redundancy or fluff, making it easy to parse quickly.

  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 one parameter with full schema coverage and no output schema, the description is minimally adequate. It covers the basic purpose and return content, but for a tool with no annotations, it should provide more behavioral context (e.g., error cases, permissions). The lack of usage guidelines and limited transparency reduces completeness, though the simple parameter schema mitigates this somewhat.

  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 100%, with the single parameter 'projectPath' well-described in the schema as 'Path to the .xcodeproj directory'. The description adds no additional parameter semantics beyond implying the tool operates on Xcode project files, which is already clear from the tool name and schema. Baseline 3 is appropriate as the schema does the heavy lifting.

  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 specific verbs ('read and parse') and resource ('.xcodeproj file'), and identifies the returned information (project structure including targets, build configurations, source files). It distinguishes from siblings like 'list-projects' (which likely lists multiple projects) by focusing on reading/parsing a single project file. However, it doesn't explicitly contrast with 'list-targets' or 'list-schemes' which might retrieve subsets of the same information.

  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. It doesn't mention when to choose 'read-project' over 'list-targets' or 'list-schemes' for getting target/scheme information, nor does it specify prerequisites or context for usage. The agent must infer usage from the purpose alone.

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

• list-schemesB
  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 states the action ('List') but does not disclose behavioral traits like whether this is a read-only operation, if it requires specific permissions, what the output format is, or if there are rate limits. For a tool with zero annotation coverage, this is a significant gap in transparency.

  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 single, efficient sentence that directly states the tool's purpose without unnecessary words. It is front-loaded with the core action and resource, making it easy to understand quickly. Every part of the sentence contributes to clarifying the tool's function.

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

  Completeness2/5

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

  Given the tool has no annotations and no output schema, the description is incomplete. It does not explain what the output looks like (e.g., list format, scheme details), behavioral aspects like error handling, or usage context. For a tool with such minimal structured data, the description should provide more context to be fully helpful.

  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?

  The input schema has 100% description coverage, with the parameter 'projectPath' fully documented in the schema. The description does not add any meaning beyond the schema, such as explaining path formats or constraints. With high schema coverage, the baseline score of 3 is appropriate, as the schema handles the parameter documentation adequately.

  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 verb ('List') and resource ('all schemes available in an Xcode project'), specifying both shared and user schemes. It distinguishes from sibling tools like 'list-projects' (which lists projects) and 'list-targets' (which lists targets), making the scope 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 'read-project' (which might include scheme information) or 'xcodebuild-info' (which could relate to build schemes). It lacks explicit when/when-not instructions or prerequisite context, such as requiring an existing Xcode project.

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

• xcodebuild-infoB
  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 states the tool retrieves information, implying a read-only operation, but doesn't clarify if it requires specific permissions, has side effects, or details the return format. This leaves significant gaps for a tool with zero annotation coverage.

  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 single, efficient sentence that directly states the tool's purpose with zero wasted words. It is appropriately sized and front-loaded, making it easy for an agent to parse quickly without unnecessary elaboration.

  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 simplicity (0 parameters, no output schema), the description adequately covers the basic purpose. However, without annotations or output schema, it lacks details on behavioral traits like error handling or return format, making it minimally viable but with clear gaps for agent usage.

  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 0 parameters with 100% schema description coverage, so the schema already fully documents the lack of inputs. The description doesn't need to add parameter details, and it appropriately focuses on the tool's purpose without redundant information, justifying a baseline score above the minimum.

  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 specific verbs ('Get') and resources ('xcodebuild version and available SDKs information'), making it immediately understandable. However, it doesn't explicitly differentiate itself from sibling tools like 'list-projects' or 'list-schemes', which prevents 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 like 'build' or 'read-project'. It lacks context about prerequisites, timing, or exclusions, leaving the agent to infer usage based solely on the tool name and purpose.

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

• list-projectsA
  4/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 effectively describes key behavioral traits: the recursive search depth limit (5 levels), exclusion of build directories, and the fact it returns 'all' matching projects. However, it doesn't mention output format, error handling, or performance characteristics.

  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 perfectly concise at two sentences. The first sentence states the core purpose, and the second adds essential behavioral details. Every word earns its place with zero redundancy or unnecessary elaboration.

  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 simple search tool with one optional parameter and no annotations, the description provides good coverage of what the tool does and its behavioral constraints. The main gap is the lack of output schema, leaving the return format unspecified. However, given the tool's simplicity, the description is reasonably complete.

  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 100%, so the schema already fully documents the single parameter. The description adds no additional parameter semantics beyond what's in the schema. The baseline score of 3 is appropriate when the schema does all the parameter documentation work.

  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 specific action ('Find all Xcode projects'), the resource type ('.xcodeproj'), and the scope ('in a directory'). It distinguishes itself from siblings like 'list-schemes' or 'list-targets' by focusing on project discovery rather than project analysis.

  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?

  The description implies usage context through the search behavior ('recursively up to 5 levels deep, excluding common build directories'), but doesn't explicitly state when to use this tool versus alternatives like 'read-project' or 'build'. No explicit exclusions or prerequisites are mentioned.

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