Server Quality Checklist

Tool Scores

• computer.system.statusB
  3.1/5.0
  Behavior3/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 adds a useful caveat that sensitive fields (username, serial, address, file info) are not returned, providing some transparency about data scope. However, it does not explicitly state that the operation is read-only, require permissions, or mention potential errors or rate limits. The 'query' verb implies read-only but doesn't make it explicit.

  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, concise sentence that is front-loaded with the action ('query') and the resource ('approval status fields'). It includes a valuable negative constraint without wasted words. Every part earns its place.

  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 (one optional parameter, output schema present), the description covers the core purpose and data boundaries. However, it omits any explanation of the 'fields' parameter, which is essential for effective use. The output schema exists, so return-value details are not needed, but the parameter semantics gap makes the description incomplete.

  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, but it completely ignores the 'fields' parameter. The tool name hints that fields relate to which status fields to query, but the description offers no explanation of parameter format, allowed values, or behavior. This is a significant gap for a tool with only one parameter.

  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: to query approval status fields of the current Mac. It also specifies what it does not return (username, serial number, address, file info), which distinguishes it from broader system info tools. This is a specific verb+resource+scope statement, though it doesn't explicitly name 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 Guidelines2/5

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

  The description gives no explicit guidance on when to use this tool versus alternatives. It implies usage for checking approval statuses, but there are no stated exclusions, prerequisites, or comparisons to sibling tools. The 'does not return' clause hints at appropriate use cases but lacks direct 'use this when' instruction.

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

• computer.work_mode.startA
  3.9/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 behavioral disclosure. It reveals the two-step confirmation gate and that confirm=true requires prior preview, which is useful. However, it does not explain side effects of starting, failure modes, or what constitutes the 'full list'.

  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?

  Two compact Chinese sentences, the first stating the purpose and the second giving the key usage instruction. Perfectly front-loaded with no filler.

  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?

  An output schema exists, so return values are covered elsewhere. The description leaves gaps about how to discover available profiles, what the 'full list' contains, and preconditions for starting the work mode. Adequate for a simple confirmation-gated tool, but not 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 coverage is 0%, so the description must compensate. It clarifies the confirm parameter's role (preview vs start) and implies profile is the work mode identifier, but it does not define profile values, format, or how it relates to the 'full list'. Partial compensation only.

  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 states the tool 'previews or starts a fixed work mode' with a specific verb+resource pairing. It clearly distinguishes itself from sibling tools like system status or app open by describing the preview/start action on work mode.

  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?

  It provides explicit usage guidance: first call with confirm=false, then pass true only after the user confirms the full list. This is clear context on how to use the tool, though it does not mention alternatives or explicit when-not-to-use scenarios.

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

• computer.app.openA
  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 behavioral burden. It discloses that the tool only opens Codex and rejects any other app, path, or URL, which is meaningful behavioral context. It omits details like foregrounding behavior or error semantics, but the output schema covers return values.

  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, front-loaded sentence states the core purpose first, then the critical constraint. Every phrase earns its place with 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?

  For a one-parameter enum-constrained tool with an output schema, the description fully defines scope, valid input, and invalid input categories. No significant gaps remain.

  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 coverage is 100% and the schema already documents the fixed lowercase value. The description adds value by clarifying that app_id cannot be a path, URL, or another application, reinforcing the parameter's meaning beyond the enum.

  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 states a specific verb ('打开' / open) and the exact target resource ('Codex'), and explicitly restricts the tool to only that app, which clearly distinguishes it from the sibling tools (system status, work mode start).

  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 gives clear when-to-use context: use it to open Codex and only Codex. It also excludes other apps, paths, and URLs, providing a when-not-to-use constraint, though it does not explicitly name alternative tools.

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