Server Quality Checklist

Tool Scores

• parse_bacnet_pcapC
  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 tool returns decoded packets and a basic device inventory, which gives some output context, but it doesn't cover critical behavioral aspects like performance characteristics, error handling, memory usage, or whether the operation is read-only or has side effects. For a tool processing network data with no annotation coverage, this is insufficient.

  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, well-structured sentence that efficiently conveys the core functionality without unnecessary details. It's front-loaded with the main action and result, making it easy to understand at a glance. Every word earns its place, with no redundancy or fluff.

  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's complexity (parsing network traffic), lack of annotations, and no output schema, the description is incomplete. It doesn't explain the format of decoded packets, what constitutes a 'basic device inventory', potential limitations, or how errors are handled. For a data processing tool with no structured output information, more context is needed to be fully helpful.

  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 description adds no parameter semantics beyond what the input schema provides. With 0% schema description coverage, the schema only lists parameter names and types without descriptions. The description doesn't explain what 'pcap_path' or 'packet_limit' mean, their formats, or constraints. However, since there are only 2 parameters and the tool's purpose is straightforward, a baseline score of 3 is appropriate as the description doesn't actively mislead but fails to compensate for the schema gap.

  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: parsing BACnet/IP traffic from a PCAP file to return decoded packets and a basic device inventory. It specifies both the verb ('parse') and resource ('BACnet/IP traffic from a PCAP'), though it doesn't explicitly differentiate from its sibling parse_modbus_pcap beyond the protocol name. This is clear but lacks explicit sibling differentiation.

  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 parse_modbus_pcap, nor does it specify prerequisites, constraints, or typical use cases. Usage is implied by the protocol name (BACnet/IP), but no explicit context or exclusions are provided.

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

• parse_modbus_pcapB
  3.4/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 parsing and returning data, but does not describe error handling, performance characteristics (e.g., time/memory usage for large PCAPs), or any limitations (e.g., supported Modbus/TCP versions). This leaves significant gaps for a tool that processes network data.

  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, well-structured sentence that efficiently conveys the tool's purpose and outputs without unnecessary details. It is front-loaded and every word contributes to understanding the tool's function.

  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 complexity of parsing network traffic, no annotations, no output schema, and low parameter coverage, the description is incomplete. It lacks details on output format (e.g., structure of transactions/inventory), error cases, and behavioral constraints, making it inadequate for informed tool selection.

  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 description does not add meaning beyond the input schema, which has 0% description coverage. It mentions 'PCAP' and 'packet limit' implicitly, but provides no details on parameter formats (e.g., file path requirements, valid ranges for packet_limit). With low schema coverage, the description does not adequately compensate, resulting in a baseline score.

  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 specific action ('Parse Modbus/TCP traffic from a PCAP') and the resources involved ('PCAP'), with explicit outputs ('return transactions plus a basic device inventory'). It distinguishes from the sibling tool 'parse_bacnet_pcap' by specifying the protocol (Modbus/TCP vs. BACnet).

  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 analyzing Modbus/TCP network traffic from PCAP files, but does not explicitly state when to use this tool versus the sibling 'parse_bacnet_pcap' or other alternatives. It provides some context (parsing PCAPs for Modbus/TCP) but lacks explicit guidance on exclusions or prerequisites.

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