Server Quality Checklist

Tool Scores

• tiktok_delete_bundleA
  3.8/5.0
  Behavior3/5

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

  With no annotations, the description carries full burden. It states the tool deletes a folder and ZIP file, implying destructive behavior, but does not disclose permissions needed, reversibility, or side effects. Minimal transparency beyond the core action.

  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: a single-line purpose followed by structured Args and Returns sections. Every sentence is informative with no redundancy, and the key action is front-loaded.

  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 delete tool with 2 parameters and an output schema, the description covers the essential: what it deletes, the arguments, and the return type. It lacks detail on error handling or edge cases, but these are less critical for a basic operation.

  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 description coverage is 0%, so the description's Args section provides crucial meaning: 'Bundle identifier' for bundle_id and 'Override default bundles directory' for bundles_dir. These explanations add value beyond the schema's titles, effectively covering both parameters.

  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 'Delete' and the resource 'a bundle folder + its ZIP file', making the tool's purpose unambiguous. It distinguishes from siblings (create, get, list) by focusing on deletion.

  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 (e.g., using delete versus other actions on bundles). There is no mention of prerequisites, when-not to use, or comparison with sibling tools.

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

• tiktok_list_bundlesA
  3.9/5.0
  Behavior3/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 tool lists bundles and allows overriding the default directory, implying a read-only behavior. However, it does not explicitly confirm no side effects, no destructive actions, or any limitations. The description is adequate but not thorough.

  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, using just a few lines to state the purpose, parameter, and return value. Every sentence adds value with no redundant information. The format is clear and front-loaded with the main action.

  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?

  The description covers the tool's purpose, the single optional parameter, and the return format (JSON array with bundle summaries). Although an output schema exists, the description provides sufficient detail for an agent to understand what is returned. For a simple list tool, this is 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?

  Schema description coverage is 0%, meaning the parameter 'bundles_dir' lacks schema-level explanation. The description compensates by explaining it overrides the default directory. This adds meaningful context beyond the raw schema type, though it could specify the default behavior more precisely.

  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 lists all prepared bundles with summary metadata. The verb 'list' and noun 'bundles' unambiguously define the action and resource. It is distinct from sibling tools that create, delete, or get individual bundles.

  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 its siblings (tiktok_create_bundle, tiktok_delete_bundle, tiktok_get_bundle). It does not mention prerequisites, exclusions, or typical use cases. The agent must infer from the name and context.

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

• tiktok_get_bundleA
  4.3/5.0
  Behavior3/5

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

  No annotations provided, and description only mentions 'Get' and return format. Lacks disclosure of side effects, auth requirements, or network usage, but for a simple read operation this is adequate.

  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?

  Very concise: states purpose, then args, then returns. No unnecessary words, front-loaded.

  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 output schema present, description covers what is needed: purpose, parameter sources, and return contents. Sibling tools are listed, and the tool is simple.

  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 0%, but description adds meaningful context: bundle_id is from list_bundles, bundles_dir overrides default directory. This compensates well.

  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?

  Clearly states 'Get full manifest for a bundle' with a specific verb and resource, and distinguishes from sibling tools (create, delete, list).

  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?

  Implies prerequisite by stating bundle_id is from list_bundles, and provides optional directory override. No explicit when-not-to-use, but siblings are distinct actions.

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

• tiktok_create_bundleA
  4.5/5.0
  Behavior4/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 discloses that the tool does not upload but prepares a local bundle, describes output files (images/, caption.txt, manifest.json, README.txt, ZIP), and specifies constraints (2-35 images, 1-2200 chars, max 30 hashtags). It lacks mention of side effects like overwriting existing bundles, but creation tools are generally non-destructive.

  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 well-structured with a clear lead sentence, bullet-like list of output files, and separate line for each argument. It is somewhat long but every sentence adds value. Could be slightly more concise by grouping some lines, but still efficient.

  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?

  Given 7 parameters, no annotations, and presence of output schema, the description is thorough. It explains the entire workflow from input to output, the rationale for manual transfer, and provides constraints for each parameter. The return format (JSON with ok, bundle_id, zip_path) is mentioned, complementing the output schema.

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

  Parameters5/5

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

  Schema description coverage is 0%, so the description adds significant value beyond the schema. It explains each parameter: images_dir (absolute path, 2-35 PNG/JPG), caption (1-2200 chars), hashtags (optional list, max 30, no '#'), series_slug (lowercase, no spaces), part_slug (optional), bundles_dir (override), make_zip (boolean, default true). It provides constraints and defaults not evident in the schema titles.

  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 tool name 'tiktok_create_bundle' clearly indicates a creation action. The description explicitly states it 'bundle[s] a folder of images + caption for TikTok mobile upload' and distinguishes from siblings (delete, get, list) by focusing on creation of a bundle for manual transfer.

  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 provides clear usage context: 'Photo carousel can only be uploaded from TikTok mobile app (not web)' and 'User then copies the ZIP/folder to their phone and uploads manually.' It does not explicitly state when not to use, but the context of manual upload implies it is not for automated posting.

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