Server Quality Checklist

Tool Scores

• get_configB
  3.2/5.0
  Behavior2/5

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

  With no annotations provided, the description carries full burden but only states what the tool does, not how it behaves. It lacks details on permissions needed, rate limits, error handling, or what 'Get' entails (e.g., is it a read-only operation, does it cache data?). This is a significant gap for a tool with zero annotation coverage.

  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 front-loads the purpose without waste. Every word contributes to clarifying the tool's function, making it appropriately sized and well-structured for its simplicity.

  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 has 0 parameters, no annotations, and no output schema, the description is minimally adequate by stating what configuration is retrieved. However, it lacks details on return values (e.g., format of configuration data) and behavioral context, which could hinder an agent's ability to use it effectively without trial and error.

  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 input schema has 0 parameters with 100% coverage, so no parameter documentation is needed. The description doesn't add parameter details, which is appropriate, earning a baseline score of 4 for not introducing unnecessary information.

  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 verb 'Get' and the resource 'current Draw Things configuration', specifying it includes 'loaded model and settings'. This is specific and unambiguous, though it doesn't explicitly differentiate from sibling tools like 'check_status' which might overlap in checking system state.

  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 like 'check_status' or other siblings. The description implies usage for retrieving configuration details but doesn't specify contexts, prerequisites, or exclusions, leaving the agent to infer based on tool names alone.

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

• transform_imageB
  3.2/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 img2img method and the requirement for an image source, but fails to describe critical behaviors such as whether the transformation is destructive to the original image, what permissions or authentication are needed, rate limits, error handling, or the output format (e.g., returns a file path or base64). For a mutation tool with zero 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 extremely concise and front-loaded, consisting of just two sentences that directly state the purpose and a key requirement. Every word earns its place with no redundancy or fluff, making it easy for an agent to parse quickly.

  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 (9 parameters, mutation operation), lack of annotations, and no output schema, the description is incomplete. It doesn't explain what the tool returns (e.g., a transformed image file or metadata), error conditions, side effects, or how it differs from siblings. For a tool that modifies images, more behavioral context is needed to ensure correct agent usage.

  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 9 parameters thoroughly with descriptions, ranges, and defaults. The description adds minimal value beyond the schema by noting the 'Either image_path or image_base64 must be provided' constraint, which isn't explicitly in the schema (though 'prompt' is required). This provides slight additional context, but most parameter semantics are covered by the schema, justifying a baseline score of 3.

  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: 'Transform an existing image using a text prompt (img2img).' It specifies the verb ('transform'), resource ('existing image'), and method ('text prompt'), distinguishing it from sibling tools like 'generate_image' (likely text-to-image) and 'check_status'. However, it doesn't explicitly contrast with 'generate_image' beyond implying img2img vs text-to-image.

  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 provides some usage context by stating 'Either image_path or image_base64 must be provided,' which helps the agent understand prerequisites. However, it lacks explicit guidance on when to use this tool versus alternatives like 'generate_image' (e.g., for modifying vs creating from scratch) or 'check_status' (e.g., for monitoring). The usage is implied but not clearly articulated.

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

• generate_imageB
  3.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 of behavioral disclosure. It states that the image 'will be saved to disk and the file path returned,' which is useful context about output behavior. However, it doesn't mention potential side effects like disk space usage, performance implications (e.g., time-intensive generation), or error conditions (e.g., invalid prompts).

  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 core purpose. It avoids unnecessary words and gets straight to the point. However, it could be slightly more structured by explicitly separating the action from the output behavior for even clearer readability.

  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?

  For a complex tool with 9 parameters and no output schema, the description is minimally adequate. It covers the basic purpose and output behavior but lacks details on error handling, performance characteristics, or integration with sibling tools. Without annotations or an output schema, more context would be helpful for an AI agent to use this tool effectively in varied scenarios.

  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, so all parameters are documented in the schema. The description adds no additional parameter semantics beyond what's in the schema. It doesn't explain relationships between parameters (e.g., how 'steps' affects quality vs. speed) or provide usage examples. The baseline of 3 is appropriate given the comprehensive schema 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 description clearly states the specific action ('Generate an image'), the resource involved ('from a text prompt'), and the tool used ('using the Draw Things app'). It distinguishes itself from sibling tools like 'transform_image' by focusing on generation rather than modification, and from 'check_status' and 'get_config' by being a creative operation rather than informational.

  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 any prerequisites, constraints, or scenarios where other tools might be more appropriate. For example, it doesn't clarify if 'transform_image' should be used for editing existing images instead of generating new ones.

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

• check_statusA
  4.1/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 the tool's purpose (connectivity/health check) but doesn't describe behavioral traits like response format, error conditions, timeout behavior, or authentication requirements. It's minimal but accurate for a simple status check.

  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 with zero waste - every word contributes essential information. Front-loaded with the core action ('Check'), followed by the target and purpose. No redundant phrases or unnecessary elaboration.

  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 simplicity (0 parameters, no annotations, no output schema), the description is complete enough to understand its basic function. However, for a connectivity check tool, additional context about what 'running and accessible' means (e.g., returns status code, response time) would be helpful despite the low complexity.

  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 tool has 0 parameters with 100% schema description coverage, so the baseline is 4. The description appropriately doesn't discuss parameters since none exist, and doesn't need to compensate for any schema gaps.

  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 ('check if... is running and accessible') and the target resource ('Draw Things API server'), distinguishing it from sibling tools like generate_image or transform_image. It uses precise language that conveys a diagnostic/health-check function rather than data manipulation.

  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 (verifying server availability before attempting operations), but doesn't explicitly state when to use this vs. alternatives or provide exclusions. It suggests a prerequisite check but lacks explicit guidance like 'use before calling generate_image if unsure about connectivity'.

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