Server Quality Checklist

Tool Scores

• search_appsA
  3.5/5.0
  Behavior3/5

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

  Annotations already provide safety info (readOnly, idempotent, non-destructive). Description adds no behavioral traits beyond the stated filters; e.g., no mention of pagination, sorting defaults, or rate limits.

  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?

  Single sentence, 16 words, no filler. Front-loaded with verb and resource. Efficiently conveys core purpose.

  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?

  Despite 11 parameters and no output schema, description omits crucial context like result format, pagination behavior, and sorting details. Schema coverage is low, leaving many parameters undocumented.

  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 coverage is only 36%, but description lists only high-level filter dimensions (keyword, category, rating, etc.) without detailing specific parameters or constraints. Many parameters (offset, sort_by, sort_dir, min_*) are not addressed, insufficiently compensating for low coverage.

  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?

  Description clearly states verb (search and filter) and resource (iOS App Store apps) and lists many filter dimensions. Distinguishes well from siblings like get_app_detail and get_app_reviews.

  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?

  Implied usage for searching/filtering, but no explicit guidance on when to use this tool vs. siblings like get_app_detail or get_app_reviews. No when-not or alternative advice.

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

• get_keyword_difficultyA
  3.6/5.0
  Behavior3/5

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

  Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint, covering the safety profile. The description adds context (iOS App Store scope) but does not disclose additional behavioral traits beyond the annotations. No contradictions.

  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?

  Single sentence, front-loaded with the key action 'Estimate difficulty and opportunity'. No redundant information or unnecessary detail. Every word earns its place.

  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?

  The description lacks explanation of the output (e.g., difficulty score range, opportunity metric). With no output schema, the agent cannot infer what the tool returns. The tool has 4 parameters and moderate complexity, so the description is insufficiently 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 description coverage is 50% (2 of 4 parameters have schema descriptions). The description does not add meaning beyond the schema; it mentions 'country' and 'language' but no detail on values or defaults. Baseline is 3 for moderate coverage.

  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 title 'Score an ASO keyword' and description 'Estimate difficulty and opportunity for one iOS App Store keyword in a country and language' clearly specify the verb (estimate), resource (keyword difficulty), and scope (iOS App Store, one keyword). It distinguishes itself from sibling tools like get_app_detail or search_apps.

  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 for keyword research on the iOS App Store, but does not explicitly state when to use this tool versus alternatives, nor does it provide conditions or exclusions. No guidance on when not to use or prerequisites is given.

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

• get_app_reviewsA
  3.8/5.0
  Behavior3/5

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

  Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint. The description adds that results include sentiment and topic signals, but does not elaborate on pagination, rate limits, or other behavioral traits beyond 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?

  A single, front-loaded sentence that efficiently conveys the tool's purpose without wasted words.

  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?

  Tool is read-only with good annotations and sibling context. However, absence of output schema means the description should ideally hint at return structure; it mentions 'rows' with sentiment/topics but lacks specifics, which is a minor gap.

  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 67% with descriptions for limit and store_id. The description adds minimal value beyond the schema, only implying the app is identified by store_id. No additional context for parameters like limit or store.

  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 'Fetch' and the resource 'App Store review rows with sentiment and topic signals'. It distinguishes from sibling tools like get_app_detail (which returns app metadata) and get_keyword_difficulty (which deals with keywords).

  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 for fetching reviews of a single iOS app but does not explicitly state when to use this tool versus alternatives like get_app_detail or search_apps. Lacks when-not-to-use guidance.

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

• get_app_detailA
  4.1/5.0
  Behavior4/5

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

  Annotations already declare readOnly, openWorld, idempotent, and non-destructive. The description adds that the tool returns metadata, ratings, and estimates, which is useful context beyond the annotations. No contradictions.

  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?

  Single sentence of 16 words, front-loaded with the core action. Every word earns its place, no redundancy.

  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 tool with one parameter and no output schema, the description adequately outlines the return categories. However, it could be more explicit about the return structure or the nature of 'directional' estimates.

  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 coverage is 0%, so the description must compensate. It mentions 'app' but does not explain the required app_id parameter format or pattern. The agent needs to infer the identifier format from the schema pattern, which is not described.

  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 retrieves a single app profile with App Store metadata, ratings, and revenue/download estimates. This verb+resource combination distinguishes it from sibling tools like get_app_reviews (reviews) and search_apps (search).

  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 use when needing detailed app data, and sibling names provide context, but there is no explicit guidance on when not to use this tool versus alternatives.

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