Server Quality Checklist

Tool Scores

• get_apk_infoA
  4.5/5.0
  Behavior4/5

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

  Annotations already declare readOnlyHint: true, and the description reinforces this by stating it does not download an APK. It also adds behavioral transparency about result semantics: 'A listing does not guarantee that a standalone APK is available,' which is valuable caveat history beyond the annotations. It does not disclose potential rate limits or error conditions, though the output schema mitigates some of that 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 compact and front-loaded: the first sentence states the action and key parameter, the next brief sentence lists the returned fields, and the final sentence adds a critical caveat. Every clause serves a distinct purpose; no filler or repeated information from the schema.

  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 tool with an output schema, the description covers the purpose, the required input format, the return fields, and an important behavioral caveat. It also differentiates from the sibling download tool. There is no missing information an agent needs to call it correctly or interpret its output.

  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 schema has 0% description coverage, but the description compensates reasonably well by defining the parameter as 'exact Android package name' and providing a concrete example (com.yolo_price_mobile). It conveys the precision requirement. However, it does not explain what happens with nonexistent or similar package names, or how the exact match is enforced.

  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 and resource ('get latest RuStore release metadata' by 'exact Android package name' with a concrete example). It clearly differentiates from the sibling tool download_apk by explicitly scoping the result to metadata and stating 'Does not download any APK.'

  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 implies when to use this tool: when you need metadata for a specific RuStore package, with emphasis on a known package name. It indirectly contrasts with download_apk by disclaiming APK download, but it does not explicitly name the alternative or provide a when-not-to-use condition beyond that exclusion.

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

• download_apkA
  4.7/5.0
  Behavior5/5

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

  Goes well beyond annotations by disclosing file output, caching, verification of manifest/signature, host prerequisites (Android SDK aapt/apksigner, Java), potential multi-minute duration, and the fact that it does not install or run the APK. No contradiction with readOnlyHint=false or destructiveHint=false.

  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?

  Every sentence earns its place: output fields, verification/caching behavior, prerequisites, runtime, and rate-limit guidance are packed in a compact, front-loaded description. The dense 'max_mib:' line is an efficient way to encode parameter constraints.

  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 two-parameter tool with an output schema, this description covers the return values, external prerequisites, runtime expectations, HTTP failure handling, and side-effect boundaries. Nothing essential is missing for correct invocation.

  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 0% schema description coverage, the description compensates by explaining that package_name is the sole required identifier and by giving max_mib's range and default (1..4096, 1024). It could more explicitly define max_mib as the maximum download size in MiB, but the title plus range is reasonably self-explanatory.

  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?

  States a specific verb ('Download'), resource ('APK from RuStore'), and input ('using just its package name'), clearly distinguishing this from a generic download or info-only sibling. The 'latest free standalone' qualifier further narrows the operation.

  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?

  Provides clear operational guidance: call sequentially for a package list and stop on HTTP 403/429. It does not explicitly say when to prefer the sibling get_apk_info instead, so it stops short of full alternative routing.

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