Server Quality Checklist

Tool Scores

• setupC
  2.5/5.0
  Behavior2/5

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

  With no annotations, the description carries full burden. It only states 'mutates: true', which is redundant given 'write', and fails to disclose side effects like overwriting existing config, required state, or whether confirmation is mandatory.

  Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

  Conciseness2/5

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

  The description is extremely brief but critically under-specified. While the first sentence is efficient, the second is redundant and overall it lacks necessary details, making it insufficient rather than concise.

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

  Completeness1/5

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

  Given the complexity of 7 parameters and the mutable nature of the tool, the description fails to cover return values, prerequisites, or any behavioral context beyond a single-line summary.

  Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

  Parameters1/5

  Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

  Input schema has 7 parameters with 0% description coverage, and the description offers no explanations for any parameter, such as the purpose of 'confirm' or format of URLs.

  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 'Write the TOML config file (first-run setup)', clearly specifying the action and resource. This distinguishes it from sibling tools like cancel_pipeline and stop_seeding, which focus on different operations.

  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 implies 'first-run' usage but provides no explicit guidance on when to use vs alternatives, nor any prerequisites or conditions for calling this tool.

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

• cancel_pipelineC
  2.6/5.0
  Behavior2/5

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

  No annotations are provided, so the description must carry the full burden. It mentions 'mutates: true', indicating state change, but it does not disclose potential side effects (e.g., whether delete_files removes data, what confirm does, or impact on seeding).

  Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

  Conciseness3/5

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

  The description is very short (one sentence plus a note), which is concise but fails to provide sufficient information. The structure is front-loaded but not adequately informative.

  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 3 parameters, no annotation support, and an output schema that is not described, the description is incomplete. It does not explain return values or behavior beyond mutation.

  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?

  With schema description coverage at 0%, the description should explain parameters. It only says 'Cancel an in-flight torrent', leaving 'infohash', 'delete_files', and 'confirm' largely unexplained beyond their names.

  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 ('Cancel') and the resource ('an in-flight torrent'), providing a specific verb and resource. However, it does not differentiate from sibling tool 'stop_seeding', which might have overlapping functionality.

  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 'stop_seeding'. There is no mention of prerequisites, context, or exclusions.

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

• stop_seedingC
  2.6/5.0
  Behavior3/5

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

  Description includes 'mutates: true' and clarifies that files are not deleted, which adds some behavioral insight beyond the action name. However, it lacks details on side effects, state changes, or permissions required.

  Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

  Conciseness3/5

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

  The description is extremely concise (one sentence plus a note), but the brevity sacrifices necessary information, especially given the lack of schema descriptions.

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

  Completeness1/5

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

  With no annotations, 0% schema coverage, and no explanation of the output schema or parameters, the description is severely incomplete for a tool requiring input parameters and producing output.

  Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

  Parameters1/5

  Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

  Schema description coverage is 0%, and the description fails to explain the two parameters (infohash and confirm). No additional meaning is provided beyond the schema structure.

  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 'Stop seeding' and distinguishes it from deletion by noting 'without deleting on-disk files'. The resource (seeding) is implied, and the sibling tools are unrelated, making the purpose stand out.

  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, nor any prerequisites or context. The sibling list doesn't include similar tools, so no comparison can be drawn.

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

• prepare_install_sourceA
  3.7/5.0
  Behavior4/5

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

  The description discloses the multi-step process, including polling with a configurable stall timeout (5 minutes default). It also notes that the tool mutates state. The return value is a path consumed by specific functions. However, failure modes, error handling, and permission requirements are not discussed.

  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 a single sentence that packs the entire process flow without redundancy. It is front-loaded with the key action. However, the sentence is somewhat run-on and could be structured into multiple sentences for clarity. Still, it is concise and each clause adds value.

  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 complexity (9 parameters, multi-step process) and absence of annotations, the description provides a high-level overview of the process and return value. It does not cover all parameters or error scenarios, but the existence of an output schema likely compensates for return value details. The description is adequate but not fully comprehensive.

  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 explain parameters. It only mentions the configurable stall timeout and implies polling interval, but does not detail the other 7 parameters (query, filters, etc.). The parameter names are somewhat self-explanatory, but the description adds minimal semantic value beyond them.

  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 purpose: search Prowlarr, hand off to qBittorrent, poll for completion, classify, and return a path for downstream consumption. It differentiates from siblings (pipeline management) by specifying a concrete resource and outcome.

  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 (preparing an install source) and mentions downstream consumers, but it does not explicitly state when to use this tool versus alternatives or provide exclusions. Sibling tools are for pipeline control, suggesting this is for setup, but no direct guidance is given.

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

• pipeline_healthA
  4.2/5.0
  Behavior4/5

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

  The description explicitly states 'mutates: false', which is the key behavioral trait given no annotations. This adds value beyond the empty schema, though it could mention additional traits like 'requires active services' or 'returns health status 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 a single concise sentence plus a key-value for mutation status. It is front-loaded and contains no extraneous information.

  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?

  The description adequately explains the tool's purpose for a simple verification tool with no parameters. It could mention that it outputs a health status, but since an output schema exists, this is not required. Still, it is largely complete.

  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?

  With zero parameters and 100% schema coverage, the description does not need to add parameter info. The baseline 4 is appropriate; it provides the necessary context for a param-free tool.

  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 it verifies reachability of Prowlarr and qBittorrent and surfaces config, using specific verbs and resources. It distinguishes from siblings which involve cancellation, preparation, setup, or stopping.

  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 use for checking connectivity but lacks explicit context, such as when to use this over siblings (e.g., before triggering other operations). No exclusions or alternatives are mentioned.

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