Server Quality Checklist

Tool Scores

• terminal_captureB
  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 that the tool captures a screenshot and returns a dictionary with base64-encoded PNG and metadata, but it does not cover critical aspects like required permissions, rate limits, error handling, or whether the capture is instantaneous or delayed. For a tool with no annotations, this leaves significant gaps in understanding its behavior.

  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 appropriately sized and front-loaded, starting with the core action and following with structured sections for Args and Returns. Every sentence earns its place by conveying key information without redundancy, though the formatting could be slightly more polished for optimal clarity.

  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 moderate complexity (single parameter, no annotations, but with an output schema), the description is partially complete. It covers the basic purpose, parameter semantics, and return structure, but lacks usage guidelines and behavioral details. The presence of an output schema reduces the need to explain return values, but overall, it falls short of being fully comprehensive for effective agent use.

  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 description adds meaningful context for the single parameter 'session_id' by specifying it as 'ID of the terminal session,' which clarifies its purpose beyond the schema's minimal title 'Session Id.' With 0% schema description coverage and only one parameter, the description effectively compensates by providing essential semantic information, though it could elaborate on format or constraints.

  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 ('Capture terminal screen as PNG screenshot') and resource ('terminal session'), distinguishing it from sibling tools like terminal_close, terminal_input, and terminal_launch. It precisely communicates what the tool does without being vague or tautological.

  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. While it implies usage for capturing screenshots of terminal sessions, it does not mention prerequisites, exclusions, or specific scenarios where this tool is preferred over others. No explicit when/when-not or alternative tool references are included.

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

• terminal_inputA
  3.7/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. It mentions sending input and a return dictionary, but lacks critical behavioral details such as whether this is a read-only or mutating operation, error handling (e.g., invalid session_id), rate limits, or how input_text and key interact (e.g., if both are provided). The description doesn't disclose enough about the tool's behavior beyond basic functionality.

  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 purpose statement followed by Args and Returns sections. It's appropriately sized and front-loaded, with each sentence adding value. Minor improvements could include integrating the sections more fluidly, but overall it's efficient with minimal waste.

  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?

  Given the tool's moderate complexity (3 parameters, no annotations, but has an output schema), the description is fairly complete. It covers the purpose, parameters, and return value. The output schema exists, so the description doesn't need to detail return values, but it could improve by addressing behavioral aspects like error cases or interaction between input_text and key.

  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 all three parameters: session_id (ID of the terminal session), input_text (text to type for alphanumeric input), and key (special key like Return, Tab, Escape). It adds meaningful context beyond the schema's titles, clarifying the purpose and usage of each parameter, though it could detail allowed values for 'key' more explicitly.

  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 ('Send input to a terminal session') and resource ('terminal session'), distinguishing it from siblings like terminal_capture (capture output), terminal_close (end session), and terminal_launch (start session). The verb 'send input' precisely defines the tool's function.

  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 by mentioning 'terminal session' and parameters like 'input_text' and 'key', but doesn't explicitly state when to use this tool versus alternatives. For example, it doesn't clarify if this should be used for all terminal input or only specific scenarios, nor does it mention prerequisites like needing an active session from terminal_launch.

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

• terminal_closeA
  4/5.0
  Behavior3/5

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

  With no annotations provided, the description carries the full burden. It discloses the action ('close') and a behavioral trait ('cleanup resources'), which implies resource management, but does not detail what cleanup entails (e.g., freeing memory, terminating processes), potential side effects, or error conditions. It adds some value but lacks depth for a mutation tool.

  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 front-loaded with the core purpose in the first sentence, followed by structured sections for Args and Returns. Every sentence earns its place by providing essential information without redundancy, making it efficient and well-organized.

  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?

  Given the tool's complexity (a mutation with cleanup), no annotations, and an output schema (which handles return values), the description is reasonably complete. It covers purpose, parameters, and returns, but could improve by adding more behavioral context (e.g., what happens on failure) to fully compensate for the lack of annotations.

  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 schema description coverage is 0%, so the description must compensate. It adds meaning by explaining that 'session_id' is the 'ID of the terminal session', which clarifies its role beyond the schema's basic type. However, it does not provide format details, examples, or constraints, leaving gaps in parameter understanding.

  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 ('Close a terminal session and cleanup resources') with the target resource ('terminal session'), distinguishing it from sibling tools like terminal_launch (create), terminal_input (send input), and terminal_capture (capture output). The verb 'close' and resource 'terminal session' are unambiguous.

  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 usage context by specifying 'close a terminal session', suggesting it should be used when a session is no longer needed, but it does not explicitly state when not to use it or name alternatives. The context is clear but lacks explicit exclusions or comparisons to siblings.

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

• terminal_launchA
  4.2/5.0
  Behavior3/5

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

  With no annotations provided, the description carries full burden. It discloses key behavioral traits: it creates a new session, uses virtual X11 display, and returns session_id and status. However, it doesn't mention important aspects like whether sessions persist, authentication requirements, resource limits, or error conditions.

  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?

  Perfectly structured with a clear purpose statement followed by organized sections for Args and Returns. Every sentence earns its place, with no redundant information. The description is appropriately sized for the tool's complexity.

  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?

  Given the tool has an output schema (returns dictionary with session_id and status), the description doesn't need to explain return values. It covers the core functionality well but could benefit from more behavioral context about session lifecycle, especially since no annotations are provided.

  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 must compensate. It provides meaningful context for all 3 parameters: command specifies what to run, width and height define terminal dimensions. The default values are clearly stated, though it doesn't explain parameter constraints or valid ranges.

  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 ('Launch a new terminal session') and distinguishes it from siblings like terminal_capture, terminal_close, and terminal_input by specifying it creates a new session with virtual X11 display rather than interacting with existing sessions.

  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 context for when to use this tool (to start a new terminal session), but doesn't explicitly state when not to use it or mention alternatives like using terminal_input for existing sessions. The sibling tool names provide implicit differentiation.

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