Server Quality Checklist

Tool Scores

• compute_runA
  4.2/5.0
  Behavior4/5

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

  The description adds important behavioral context beyond annotations: commands run non-interactively, the tool syncs the local project, and 'the command has the full permissions of the remote SSH user.' These details complement the destructiveHint and readOnlyHint annotations without contradiction.

  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 concise sentences each carry unique information: purpose, use cases, a warning to keep edits local, and the permission warning. There is no redundant or filler content.

  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 (8 params, output schema, annotations), the description covers the core workflow (sync and run), the intended use cases, and the security implications. It does not need to restate schema details, making it complete enough for an agent to decide when and how to invoke it.

  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 already provides 100% parameter coverage with detailed descriptions, so the description adds minimal parameter-level value. The note about running 'non-interactive' commands is useful context but the schema already explains shell syntax for program/arguments.

  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 specific verbs 'Sync' and 'run' with the resource 'Tailscale compute node', clearly distinguishing it from the sibling tool compute_status. It also enumerates use cases (builds, tests, benchmarks) that make the tool's purpose 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 description explicitly states 'Use it for builds, tests, benchmarks, and other costly work', giving the agent clear when-to-use guidance. While it does not mention when not to use it, the sibling tool compute_status is obviously for status checks, so the context is sufficient.

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

• compute_statusA
  4.3/5.0
  Behavior4/5

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

  Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false. The description adds specific behavioral context by detailing the types of information reported and positioning it as a pre-flight check, which is useful beyond the 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 two sentences with front-loaded purpose and no unnecessary words. Every phrase adds value, including the usage guidance.

  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?

  With a single optional parameter, full annotations, and an output schema, the description provides sufficient context to invoke the tool correctly and understand when it is needed. The explicit usage scenarios complete the picture.

  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 provides 100% coverage with a clear description for the single parameter, including when to omit it. The description itself adds no parameter-specific meaning, so the baseline 3 is appropriate.

  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 'Check the configured Tailscale compute node and report its operating system, hardware, remote shell, and accelerator inventory.' This is a specific verb+resource+output list that distinguishes it from the sibling compute_run by indicating a status check before running.

  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 explicitly says 'Use this before the first remote run or after a connection failure,' providing clear timing guidance. It does not explicitly state when not to use it or name alternatives beyond the sibling context, but the usage context is strong.

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