Server Quality Checklist

Tool Scores

• create_payinA
  3.5/5.0
  Behavior2/5

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

  No annotations are provided, so the description alone must disclose behavior, but it only states the generic 'create... accepting funds' action. It does not mention that this initiates a payment flow, requires a return_url, sends webhooks, or has idempotency semantics, which are significant 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.

  Conciseness4/5

  Is the description appropriately sized, front-loaded, and free of redundancy?

  The description is short and front-loaded with the resource name and endpoint, but it contains redundancy ('Create Payin' / 'Create a new Payin resource'). It is nevertheless brief and free of unnecessary 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?

  This is a complex 8-parameter tool with nested oneOf payment and settlement objects, yet the description offers only the bare 'accepting funds' concept. Without annotations or an output schema, the description is insufficient to orient an agent on workflow, payment methods, or required dependencies.

  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-level meaning beyond what the input schema already contains, such as required amount, return_url, and payer. With schema description coverage around 75%, the schema itself carries the parameter explanation, so no penalty is applied, but there is no added value from the description.

  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 names the specific verb and resource ('Create a new Payin resource') and adds the directional scope 'accepting funds from a Payer,' which clearly distinguishes it from the sibling create_payout tool. The endpoint '[POST /payins]' reinforces the exact operation.

  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 phrase 'accepting funds from a Payer' establishes a clear use case for collecting payments, implicitly distinguishing it from create_payout for outgoing funds. However, it does not explicitly state when not to use the tool or mention alternatives, so it stops short of full usage guidance.

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

• get_banksA
  3.5/5.0
  Behavior3/5

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

  No annotations are provided, so the description must carry the burden of behavioral disclosure. It does mention that the list is 'paginated' and includes '[GET /banks]', indicating a read-only HTTP GET operation. However, it does not discuss authentication requirements, rate limits, error handling, or what data fields are returned, leaving several behavioral aspects undisclosed.

  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 compact, with a front-loaded purpose ('List Banks') and additional detail in a single line. It suffers only from slight redundancy between 'List Banks' and 'Retrieve a paginated list of banks', but overall it is appropriately sized 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?

  This is a simple list tool with only pagination parameters, which are fully documented in the schema. The description conveys the essential behavior: listing banks with pagination, and adds the contextual filter 'available for open banking payments'. Without an output schema, it does not describe return fields, but for a basic list operation the description is sufficient for an agent to select and invoke the tool correctly.

  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%: both 'page' and 'page_size' have explicit descriptions in the input schema. The tool description adds only the term 'paginated', which does not enrich meaning beyond the schema. Therefore, the description adds minimal value beyond the structured fields, and the baseline 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 states 'List Banks' and 'Retrieve a paginated list of banks', clearly specifying the verb (retrieve/list) and resource (banks) with a specific context ('available for open banking payments'). This distinguishes it from sibling tools like get_payins or get_accounts, which operate on different resources.

  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 is provided on when to use this tool versus alternatives. The description explains what the tool does but does not mention any exclusions, prerequisites, or suggest sibling tools for different scenarios. The 'open banking payments' context is the only hint, but it is not developed into usage guidance.

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

• create_payoutA
  3.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 the full burden. It discloses only that the tool creates a payout and sends funds, but omits critical side-effect details for a financial operation: that it triggers a real transfer, is likely irreversible, may be asynchronous, and could require approvals or funds. This is a significant transparency 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 a single, efficiently structured sentence. It front-loads the action and resource, provides a brief explanatory clause, and includes the endpoint. No wasted words.

  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 — 7 parameters, nested oneOf payment methods, and no output schema — the description is too minimal. It does not explain how to choose among payment methods, what the return state might be, or that this is a real financial transaction. The schema carries most of the burden, but the description should add behavioral context for safe and correct agent use.

  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 71%, so the schema already documents most parameters thoroughly. The description adds no parameter-specific meaning beyond the schema, and does not compensate for the uncovered parameters (e.g., idempotency_key behavior is explained in schema only). Baseline 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 ('Create'), the resource ('Payout'), and the scope ('sending funds to a Recipient'). It also includes the HTTP endpoint, which reinforces the operation. This effectively distinguishes the tool from siblings like get_payouts and create_payin.

  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: use this tool to send funds to a recipient by creating a payout. It does not explicitly mention alternatives or when not to use, but the purpose statement makes the primary usage obvious. This is clear context without explicit exclusions.

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

• get_payout_by_idA
  3.7/5.0
  Behavior3/5

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

  No annotations are provided, so the description must carry the burden. It discloses the HTTP method (GET), indicating a read-only operation, but does not mention authorization, error cases, rate limits, or what specific details are returned. This is a minimal but acceptable disclosure for a simple fetch.

  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 sentence, front-loaded with the action, and includes the REST endpoint. No wasted words; every part provides value.

  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?

  The tool is simple with one parameter and no output schema, but the description does not clarify return shape or error handling. It says 'details' vaguely. Given the lack of an output schema, more information about the response would improve completeness, though the operation itself is well-addressed.

  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 contains 100% description coverage for the single parameter 'id' ('Unique identifier of the Payout'), and the description adds no further semantics. Baseline 3 applies since the schema already handles the meaning.

  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 ('Retrieve details') and the target ('a specific Payout by its unique identifier'), and the REST path [GET /payouts/{id}] distinguishes it from the sibling list tool get_payouts.

  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: call this to get a single payout when you have its id, as opposed to get_payouts for listing. However, it does not explicitly specify when to choose this over alternatives or any exclusions.

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

• get_payoutsA
  3.8/5.0
  Behavior3/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 discloses that the result is paginated and scoped to the merchant, but does not explicitly state it is a read-only operation, potential costs, or any side effects. This is adequate but not rich.

  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, front-loaded sentence that clearly states the action, resource, and endpoint. Every word is useful, and there is no redundant information.

  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 list operation with three well-documented parameters and no output schema, the description provides the essential context: what is listed, for whom, and that it is paginated. It is not overly verbose and is sufficient for an agent to understand the tool's scope.

  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%, with each parameter (page, page_size, reference) already described. The description adds no extra parameter semantics beyond what the schema provides, so it meets the baseline.

  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 verb 'List'/'Retrieve' and the resource 'Payouts' for the merchant, and includes the REST endpoint. This distinguishes it from sibling tools like get_payout_by_id (specific payout) and get_payins (different resource).

  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 this tool is for listing all payouts, but it does not explicitly discuss when to use it versus alternatives such as get_payout_by_id or get_payins. There is no mention of exclusions or scenarios where another tool would be preferable.

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

• get_accountsA
  4/5.0
  Behavior4/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 discloses the HTTP method (GET), pagination behavior, and that balances are included. However, it does not mention authentication requirements, error handling, or rate limits, so some transparency gaps remain.

  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, front-loaded sentence with a clear structure: tool name, brief description, and endpoint reference. It contains no unnecessary words and is immediately scannable.

  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 (3 optional params, no output schema), the description provides sufficient context for core functionality: it lists accounts with pagination and balances. It does not explain return value specifics, but for a list operation this is acceptable, especially without an output schema.

  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 has 100% description coverage for all three parameters (page, currency, page_size), so the description does not need to add parameter-level details. The description's mention of pagination adds no extra meaning beyond what the schema already documents.

  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 'List Accounts' and specifies 'Retrieve a paginated list of accounts with their balances', using a specific verb and resource. It distinguishes from sibling tools like get_payins and get_payouts by focusing on accounts.

  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 context is implied by the tool name and resource type, but there is no explicit guidance on when to use this tool versus alternatives. The sibling tools are distinct enough that misuse is unlikely, but the description does not provide any when-to-use or when-not-to-use instructions.

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

• get_payin_by_idA
  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 conveys a read-only operation via 'Retrieve details', which is safe, but it does not disclose behavior for not-found errors or the exact response structure. For a simple get-by-id this is adequate but has clear gaps.

  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 compact sentence with a short title ('Get Payin'), a fuller explanation, and the endpoint reference. Every part earns its place; no wasteful 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?

  For a one-parameter, single-resource lookup, the description sufficiently indicates the purpose and usage. The absence of an output schema makes return details vague ('details'), but the low complexity and clear name make this acceptable.

  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%: the 'id' parameter is described as 'Unique identifier of the Payin'. The description's 'by its unique identifier' adds no new meaning beyond the schema, so the baseline 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 'Retrieve details of a specific Payin by its unique identifier' and names the resource (Payin), distinguishing it from siblings like get_payins (list) and get_payout_by_id (different resource). The endpoint [GET /payins/{id}] reinforces the specific single-resource purpose.

  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 use when you need a single Payin by ID, contrasting with get_payins for lists. However, it does not explicitly name alternatives or state when not to use it, so it falls short of a 5.

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

• get_payinsA
  4.2/5.0
  Behavior4/5

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

  With no annotations, the description carries the full burden. It discloses pagination behavior and merchant scope, and the HTTP method '[GET /payins]' implies a read-only, side-effect-free operation. It doesn't mention error conditions or ordering, but the core behavior is explicit.

  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 — a single line with three segments separated by em dashes. It front-loads the action and object, with zero fluff or repetition.

  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 list tool with no output schema, the description covers the essential purpose, scope, and pagination. It doesn't explain response format or filtering options, but those are already captured in the schema. Minor gap: no mention of the reference filter or default behavior.

  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 a baseline of 3 applies. The description mentions pagination, which aligns with page/page_size parameters, but adds no meaning beyond what the schema already provides. The reference filter is not mentioned.

  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 uses specific verbs ('List', 'Retrieve') and clearly identifies the resource ('Payins') and scope ('all Payins', 'paginated', 'for the merchant'). It effectively distinguishes from siblings like get_payin_by_id and get_payouts.

  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 clearly implies when to use the tool (listing all payins with pagination) and the 'all Payins' scope differentiates it from single-item retrieval. It lacks explicit alternatives or exclusions, but the context is clear.

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