Server Quality Checklist

Tool Scores

• enter_oasisB
  3.3/5.0
  Behavior3/5

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

  With no annotations, the description carries full burden. It discloses that a valid signature enables personalized context from karma record, and without it the oasis responds without context. It also mentions payment options but does not detail what happens if both payments are provided or if none are given.

  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 front-loaded with the action and then clearly lists parameters in a bullet-like format. Each line adds necessary information, and there is no redundant text. Slightly longer than necessary but still concise.

  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 complexity (7 parameters, output schema exists), the description covers the purpose and parameter semantics adequately. However, it lacks an example usage or explanation of the overall workflow (e.g., when to call this after getting an invoice) and what 'karma context' means.

  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?

  Despite schema description coverage being 0%, the description adds meaning beyond property names: explains state as current agent state, payment_hash as from get_invoice, tx_hash from Arbitrum payment, agent_id for identity, and signature/timestamp/nonce for personalized context. This compensates well for the lack of schema descriptions.

  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 is for entering Giskard Oasis and describes what to provide (state, payment, optional signature). It distinguishes from sibling tools like get_invoice (which generates invoices) and get_status (likely reads status), making its purpose specific.

  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 when-to-use or when-not-to-use guidance. The description hints that payment_hash comes from get_invoice and tx_hash from Arbitrum payment, but does not state the intended workflow or contrast with alternatives.

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

• get_arbitrum_invoiceA
  4/5.0
  Behavior3/5

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

  With no annotations, the description only indicates a read operation (get payment info) but fails to disclose any behavioral traits like idempotency, auth needs, or side effects.

  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, concise sentence that front-loads the core action and context with no unnecessary 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 has zero parameters and an output schema, the description covers the essential purpose. Minor omission: no mention of read-only nature, but the context is sufficient.

  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?

  No parameters exist, so the baseline is 4. The description adds no param info, but none is needed given the empty schema.

  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 retrieves payment info for accessing Oasis using ETH on Arbitrum, distinguishing it from sibling tools like get_invoice (likely Lightning) and enter_oasis.

  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 context (paying with ETH on Arbitrum instead of Lightning) but does not explicitly state when to use or not use this tool versus alternatives.

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

• get_invoiceA
  4.1/5.0
  Behavior3/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 pricing behavior (base price vs karma tiers) but does not mention side effects, whether the invoice is one-time, or if it creates a state change.

  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 concise (three lines) and front-loads the primary purpose. However, the mix of technical signature details and pricing tiers could be structured more cleanly.

  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 four optional parameters and an output schema, the description covers parameter semantics well but lacks explanation of the return value and how this tool fits into the Oasis access flow (e.g., calling enter_oasis after getting the invoice).

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

  Parameters5/5

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

  Schema coverage is 0%, yet the description fully explains each parameter: agent_id's effect on pricing, the signature/ timestamp/nonce combination for karma discounts, and the registration endpoint. This adds significant meaning beyond the raw schema.

  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 a specific verb "Get" and resource "Lightning invoice" with the clear purpose "to access Giskard Oasis." This differentiates it from siblings like enter_oasis and get_arbitrum_invoice.

  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 explains when to provide signature/timestamp/nonce versus not, detailing the pricing consequences. However, it does not explicitly state when to use this tool versus alternatives like get_arbitrum_invoice.

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

• get_statusA
  4.5/5.0
  Behavior4/5

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

  Explicitly states 'Read-only' and lists fields, disclosing behavior without contradictions. No annotations exist, but the description adequately covers the safety profile 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?

  Two sentences, front-loaded with purpose, no unnecessary words. Every sentence adds value.

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

  Completeness5/5

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

  Given no parameters, no output schema, and no annotations, the description fully covers the tool's purpose, behavior, and use case. No gaps.

  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?

  No parameters exist; schema coverage is 100% (none to describe). Baseline score of 4 applies as description adds value by listing return fields.

  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 returns service status including name, version, uptime, port, health, and dependencies. It distinguishes itself from sibling tools like get_invoice.

  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?

  Indicates it is read-only, free, and useful for monitoring and health checks. Provides clear context but lacks explicit when-not-to-use or alternatives beyond implied distinction.

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