Server Quality Checklist

Tool Scores

• locate_ipC
  2.9/5.0
  Behavior2/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 of behavioral disclosure. It mentions the output format but doesn't describe error handling, rate limits, authentication needs, or whether the tool is read-only or has side effects. For a tool with no annotation coverage, this is a significant gap in transparency.

  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, efficient sentence that front-loads the purpose and output. It avoids unnecessary words, though it could be slightly more structured (e.g., separating purpose from output details).

  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 tool's low complexity (1 parameter, no nested objects) and the presence of an output schema, the description is minimally adequate. However, it lacks behavioral context (e.g., error cases, performance), which is needed since no annotations are provided. The output schema likely covers return values, so the description doesn't need to detail them.

  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 has 100% description coverage, with the parameter 'ip' documented as '用户的ip地址' (user's IP address). The description doesn't add meaning beyond the schema, such as explaining default behavior when 'ip' is null or providing examples. Baseline 3 is appropriate since the schema does the heavy lifting.

  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 tool's purpose: '获取用户的 IP 地址定位信息' (get user's IP address location information) and specifies the output '返回省市区经纬度等信息' (returns province, city, district, latitude/longitude, etc.). It uses specific verbs and resources, though it doesn't explicitly differentiate from the sibling tool 'search_nearby'.

  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 alternatives like 'search_nearby'. It lacks context about use cases, prerequisites, or exclusions, leaving the agent to infer usage from the purpose alone.

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

• search_nearbyB
  3.1/5.0
  Behavior2/5

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

  With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions the basic operation (search and return POI list) but doesn't describe important behavioral aspects like whether this is a read-only operation, potential rate limits, authentication requirements, error conditions, or what happens when no results are found. For a search tool with 6 parameters and no annotation coverage, this is a significant 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 a single, efficient sentence that states the core functionality without unnecessary words. It's appropriately sized for the tool's complexity and front-loads the essential information (search based on location/keywords, returns POIs within radius). Every word earns its place.

  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 that there's an output schema (which should document return values), no annotations, and 100% schema coverage for parameters, the description provides adequate basic context. However, for a search tool with pagination parameters and no behavioral annotations, the description could better address usage patterns, result limitations, or common scenarios. It's minimally viable but lacks depth for optimal agent understanding.

  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 100%, so the schema already documents all 6 parameters thoroughly. The description mentions '经纬度和关键词' (longitude/latitude and keywords) and '指定半径' (specified radius), which aligns with parameters in the schema but doesn't add meaningful semantic context beyond what's already in the parameter descriptions. Baseline 3 is appropriate when the schema does the heavy lifting.

  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 tool's purpose: '根据经纬度和关键词进行周边搜索，返回指定半径内的 POI 列表' (Search nearby based on longitude/latitude and keywords, returning a list of POIs within a specified radius). It specifies the verb ('搜索' - search), resource ('POI 列表' - POI list), and scope ('周边' - nearby/within radius). However, it doesn't explicitly differentiate from the sibling tool 'locate_ip', which appears to be a different type of location tool.

  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 alternatives. It doesn't mention the sibling tool 'locate_ip' or any other potential alternatives. There's no information about prerequisites, appropriate contexts, or when this tool would be preferred over other search or location tools.

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