Server Quality Checklist

Tool Scores

• bond_declineA
  3.8/5.0
  Behavior3/5

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

  No annotations exist, so the description carries the full burden. It discloses that the file is discarded and the sender is not notified, which is useful. However, it does not mention irreversibility, permission requirements, or other behavioral details.

  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 two sentences with no wasted words. The action is stated first, followed by consequences, making it easy to parse.

  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 low complexity (one parameter, no output schema), the description is mostly complete. It covers the main action and outcome, though it omits potential reversibility or confirmation steps.

  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 coverage is 100% for the single parameter, so the baseline is 3. The description adds no extra meaning beyond the schema's 'Transfer ID from the consent prompt'.

  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 action ('Decline a pending file transfer') and its immediate effect ('File will be discarded and sender will not be notified'). This distinguishes it from sibling tools like bond_accept, bond_end, etc.

  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?

  Usage is implied for rejecting a pending transfer, but there is no explicit guidance on when to use this tool versus alternatives. No when-not conditions or prerequisites are provided.

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

• bond_endA
  4/5.0
  Behavior4/5

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

  The description clearly states the tool ends the session and clears pending transfers, which is useful behavioral info. However, it does not disclose potential side effects like data loss or confirmation requirements. Given no annotations, the description carries full burden and is mostly adequate.

  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: two sentences, no wasted words, immediately front-loads the key action. Every sentence earns its place.

  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?

  For a simple tool with no parameters and no output schema, the description covers the main action (end session, disconnect, clear transfers). It lacks details about error states or prerequisites, but the action is straightforward, so completeness is high.

  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 no parameters, so schema coverage is 100% by default. The description does not need to add parameter meaning. According to guidelines, baseline is 4 for 0 parameters, and the description meets this bar.

  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 tool ends the current Covalent Bond session, disconnects from relay, and clears pending transfers. It uses a specific verb (end) and resource (session), and distinguishes from siblings (bond_accept, bond_decline, bond_join, bond_send) which handle other actions.

  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. The description does not mention prerequisites or when not to use it. While sibling names imply usage contexts, the description lacks direct recommendations.

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

• bond_acceptA
  4.2/5.0
  Behavior5/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 clearly discloses that the file is written to '~/.covalent/incoming/' and the content is returned wrapped in 'untrusted-data markers', which warns about potential security risks. No contradictions or missing behavioral traits.

  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 two sentences long with no unnecessary words. It front-loads the core purpose ('Accept a pending file transfer') and efficiently conveys key behavioral details. No wasted content.

  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 simple one-parameter tool with no output schema, the description adequately covers the main behavior: file writing location, content return, and untrusted-data warning. It could mention side effects (e.g., transfer no longer pending, file removal) or error conditions, but the core completeness is high for the tool's complexity.

  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 coverage is 100% (transferId is described as 'Transfer ID from the consent prompt'). The description does not add any parameter-level details beyond the schema. Per the high-coverage baseline, a score of 3 is appropriate.

  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 action: 'Accept a pending file transfer.' It also specifies the outcome (file written to path, content returned with untrusted-data markers), which distinguishes it from sibling tools like bond_decline (decline), bond_send (send), bond_end (end), and bond_join (join).

  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 when a pending file transfer exists and the agent wants to accept it. However, it does not explicitly state when not to use (e.g., when transfer is already accepted) or mention alternatives (e.g., bond_decline for declining). The usage context is implied but not spelled out.

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

• bond_sendA
  4.2/5.0
  Behavior5/5

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

  With no annotations, the description fully conveys behavioral traits: encryption, rate limiting (10-second), file type whitelist, configurable size limit (256KB). This empowers the agent to anticipate and handle constraints without additional discovery.

  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?

  Two sentences. The first sentence front-loads the core purpose; the second adds critical behavioral constraints. No extraneous words.

  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 simplicity (2 parameters, no output schema), the description covers purpose, security, and limits. It omits potential error handling or confirmation details, but remains largely sufficient.

  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 coverage is 100%, already describing both parameters ('message' as optional context, 'filepath' as absolute path). The description adds no new parameter information, so the baseline score of 3 applies.

  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 action ('Send a file') and the recipient ('to the connected agent'). It distinctly sets this tool apart from its siblings (bond_accept, bond_decline, etc.), which handle other bond lifecycle steps.

  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 when to use the tool (to send a file) but does not explicitly contrast with siblings or provide when-not-to-use guidance. Constraints such as rate limits and size limits are mentioned, which help inform usage decisions.

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

• bond_joinA
  4.4/5.0
  Behavior4/5

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

  No annotations provided, so description bears full burden. Discloses that session code is a shared secret, authenticates channel, and is never sent to relay. Does not detail error behavior or side effects, but security implication is clear.

  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?

  Two sentences, front-loaded with action verb, no redundant words. Every sentence adds value.

  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 simple tool (1 param, no output schema, no annotations), description covers core purpose, usage trigger, and security context. Missing potential failure modes but schema regex handles format validation.

  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?

  Single parameter, schema coverage 100%. Description adds format example but does not add substantial meaning beyond schema. Baseline 3 appropriate.

  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?

  Specific verb 'Join' + resource 'Covalent Bond session' + qualifier 'using a session code'. Distinguishes from siblings like bond_accept (accepting an invitation) and bond_end (ending session). Format and example provided.

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

  Usage Guidelines5/5

  Does the description explain when to use this tool, when not to, or what alternatives exist?

  Explicit call condition: 'Call this when the user provides a session code from another agent.' Implies when not to use, and context clearly distinguishes from other bond tools.

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