Server Quality Checklist

Tool Scores

• send_emailD
  1.6/5.0
  Behavior1/5

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

  With no annotations provided, the description carries full burden for behavioral disclosure but offers none. It doesn't mention authentication requirements (despite username/password parameters), rate limits, error conditions, whether the operation is idempotent, or what happens on success/failure. For a mutation tool with 9 parameters, this lack of behavioral context is critically inadequate.

  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 extremely concise - a single Korean sentence. While this is efficient, it's arguably under-specified rather than appropriately concise given the tool's complexity. However, it does front-load the core purpose without unnecessary elaboration, earning points for brevity.

  Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

  Completeness1/5

  Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

  For a mutation tool with 9 parameters (including complex nested objects for attachments), no annotations, 0% schema description coverage, and no output schema, the description is completely inadequate. It provides no information about authentication, parameter usage, return values, error handling, or behavioral characteristics that an agent needs to use this tool effectively.

  Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

  Parameters1/5

  Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

  Schema description coverage is 0%, meaning none of the 9 parameters have descriptions in the schema. The tool description provides no information about any parameters, their purposes, formats, or relationships. This leaves critical parameters like 'attachments' (with nested objects) completely undocumented, failing to compensate for the schema's deficiencies.

  Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

  Purpose2/5

  Does the description clearly state what the tool does and how it differs from similar tools?

  The description '하이웍스 이메일을 전송합니다' (Sends Hiworks email) states the basic action but is tautological with the tool name 'send_email'. It doesn't specify what distinguishes this email sending tool from potential alternatives or clarify the scope beyond the obvious verb+resource pairing. While it identifies the service (Hiworks), it lacks specificity about capabilities or constraints.

  Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

  Usage Guidelines1/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 the sibling tools (read_email, read_username, search_email). The description doesn't mention prerequisites, appropriate contexts, or exclusions. An agent would have to infer usage from the tool name alone without any contextual direction.

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

• search_emailC
  2.1/5.0
  Behavior1/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 but fails to do so. It does not mention authentication needs (despite username/password parameters), rate limits, output format, or any behavioral traits. This leaves critical operational details unspecified.

  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 with no wasted words. It is appropriately sized and front-loaded, stating the core action and system without unnecessary elaboration, making it highly concise.

  Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

  Completeness1/5

  Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

  Given the complexity of a search tool with 4 parameters, no annotations, and no output schema, the description is incomplete. It lacks details on authentication, search scope, result handling, and behavioral context, failing to provide sufficient information for effective tool use.

  Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

  Parameters1/5

  Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

  Schema description coverage is 0%, and the description adds no meaning beyond the schema. It does not explain parameters like 'username', 'password', 'query', or 'limit', nor their roles or formats. For a tool with 4 parameters, this lack of semantic information is inadequate.

  Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

  Purpose3/5

  Does the description clearly state what the tool does and how it differs from similar tools?

  The description states the tool's purpose ('search emails') and specifies the system ('Hiworks'), which provides basic clarity. However, it lacks specificity about what aspects of emails are searched (e.g., subject, body, sender) and does not differentiate from sibling tools like 'read_email' or 'send_email', making it somewhat vague.

  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 such as 'read_email' or 'send_email'. The description implies usage for searching emails but offers no context on prerequisites, exclusions, or comparative scenarios, leaving the agent without direction on tool selection.

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

• read_usernameC
  2.4/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 offers minimal behavioral insight. It implies a read operation but doesn't disclose authentication needs (despite username/password parameters), rate limits, error conditions, or what the return value looks like. This is inadequate for a tool with parameters.

  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 with no wasted words. It's appropriately sized for a simple tool, though it could be more informative without sacrificing brevity.

  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?

  For a tool with 2 parameters, 0% schema coverage, no annotations, and no output schema, the description is insufficient. It doesn't explain parameter usage, return values, or behavioral context, making it incomplete for effective agent use.

  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 description coverage is 0%, so the description must compensate but doesn't mention parameters at all. The two parameters (username, password) are undocumented in both schema and description, leaving their purpose and usage unclear. The description adds no value beyond the schema.

  Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

  Purpose3/5

  Does the description clearly state what the tool does and how it differs from similar tools?

  The description '하이웍스 username을 읽어옵니다' (Reads Hiworks username) states a clear verb+resource action, but it's somewhat vague about what exactly is being read. It doesn't distinguish from sibling tools like read_email or search_email, leaving ambiguity about whether this reads a specific user's username or lists usernames.

  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 read_email or search_email. The description doesn't mention prerequisites, context, or exclusions, leaving the agent with no usage direction beyond the basic purpose.

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

• read_emailC
  2.6/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 full burden. It states the action ('read') but doesn't disclose behavioral traits such as authentication needs (implied by username/password parameters), rate limits, error handling, or what 'read' returns (e.g., full email content). This leaves significant gaps for a tool with authentication parameters.

  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 in Korean with no wasted words. It's front-loaded with the core action and resource, making it easy to parse quickly. Every word contributes to stating the purpose without redundancy.

  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 (3 parameters, authentication, no output schema, and no annotations), the description is incomplete. It doesn't cover parameter meanings, return values, or behavioral context. For a tool that likely involves sensitive data (email) and authentication, more detail is needed to be fully usable by an AI agent.

  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 description coverage is 0%, so the description must compensate. It doesn't mention any parameters, leaving all three (username, password, messageId) undocumented. The description adds no meaning beyond the schema, failing to explain what 'messageId' refers to or why authentication is needed, which is critical given the low coverage.

  Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

  Purpose3/5

  Does the description clearly state what the tool does and how it differs from similar tools?

  The description '하이웍스 이메일을 읽어옵니다' (Reads Hiworks email) states a clear verb ('read') and resource ('Hiworks email'), but it's vague about scope and doesn't distinguish from sibling tools like 'search_email'. It specifies the service (Hiworks) but lacks detail on what 'read' entails (e.g., fetching a single email vs. listing).

  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 explicit guidance on when to use this tool versus alternatives like 'search_email' or 'send_email'. The description implies it's for reading emails, but doesn't specify scenarios (e.g., for a specific message ID) or exclusions. Usage is implied from the name and context, but no practical advice is provided.

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