Server Quality Checklist

Tool Scores

• pot_verifyC
  2.9/5.0
  Behavior2/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 the tool returns validity, mode, and timestamp, but lacks details on error handling, rate limits, authentication needs, or side effects. For a verification tool with four required parameters, this leaves significant gaps in understanding its operational behavior.

  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 action (verify) and key inputs. It avoids redundancy and wastes no words, though it could be slightly more structured by separating purpose from output details for clarity.

  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 (four required parameters, no annotations, no output schema), the description is insufficient. It doesn't explain the verification process, potential outputs beyond a vague list, or how results should be interpreted. For a tool with cryptographic inputs and no structured output, more context is needed to ensure correct 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?

  The schema description coverage is 100%, so the input schema fully documents all four parameters. The description adds minimal value beyond this, only implying that potHash and grgShards are used for verification. It doesn't explain relationships between parameters or provide usage examples, meeting the baseline for high schema coverage.

  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: verifying a Proof of Time using hash and GRG shards, and specifies what it returns (validity, mode, timestamp). It distinguishes from siblings like pot_generate (creation) and pot_query (querying) by focusing on verification. However, it doesn't explicitly contrast with pot_health or pot_stats, keeping it from a perfect score.

  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 like pot_query or pot_stats. It mentions the required inputs but doesn't specify prerequisites, error conditions, or typical use cases. Without such context, users must infer usage from the purpose alone.

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

• pot_generateB
  3.1/5.0
  Behavior2/5

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

  With no annotations, the description carries full burden but lacks behavioral details. It mentions the return values (potHash, timestamp, stratum, GRG integrity shards) but doesn't disclose critical traits like whether this is a read-only or mutating operation, authentication needs, rate limits, or error conditions. The output description is helpful but insufficient for full transparency.

  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 and key output details. Every word earns its place with no redundancy or fluff, making it highly concise and well-structured.

  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 3 parameters with full schema coverage and no output schema, the description is minimally adequate. It explains the purpose and outputs but lacks context on when to use, behavioral traits, or error handling. For a tool with no annotations, it should do more to compensate, but the output details provide some completeness.

  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 fully documents parameters (txHash, chainId, poolAddress). The description adds no parameter-specific semantics beyond what the schema provides, such as format examples or constraints. Baseline 3 is appropriate as the schema does the heavy lifting.

  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 action ('Generate a Proof of Time') and the resource ('for a transaction'), with specific output details. It distinguishes from siblings like pot_health or pot_stats by focusing on generation rather than monitoring or verification, though it doesn't explicitly contrast with pot_query or pot_verify.

  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 pot_verify (which might validate proofs) or pot_query (which might retrieve existing proofs). The description implies usage for generating proofs but offers no context about prerequisites, timing, or exclusions.

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

• pot_queryB
  3.1/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 without behavioral details. It doesn't disclose whether this is a read-only operation, potential rate limits, authentication needs, or what happens if data sources are unavailable. For a query tool with zero annotation coverage, this leaves significant gaps in understanding its behavior.

  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 zero wasted words. It front-loads the core purpose ('Query Proof of Time history') and specifies data sources concisely. Every element earns its place without redundancy.

  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 moderate complexity (querying multiple data sources), lack of annotations, and no output schema, the description is minimally adequate. It states what the tool does but doesn't explain return values, error conditions, or behavioral traits. With 100% schema coverage, parameters are well-documented, but overall completeness is limited for a query tool without output details.

  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 input schema fully documents all three parameters with defaults and constraints. The description adds no additional parameter semantics beyond implying time-based filtering, which is already covered in the schema. This meets the baseline for high schema coverage.

  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 action ('Query') and resource ('Proof of Time history'), specifying both data sources ('local log and on-chain subgraph'). It distinguishes from siblings like 'pot_generate' or 'pot_verify' by focusing on retrieval rather than creation or validation. However, it doesn't explicitly contrast with 'pot_stats' which might also involve querying.

  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 'pot_stats' or 'pot_verify'. The description implies it's for historical queries, but there's no explicit context, prerequisites, or exclusions mentioned to help an agent choose between sibling tools.

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

• pot_statsB
  3.1/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 implies a read-only operation ('Get') but does not specify data sources, permissions required, rate limits, error handling, or whether the statistics are real-time or cached. For a tool with zero annotation coverage, this leaves significant gaps in understanding its behavior and constraints.

  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 key action and metrics without any wasted words. It directly communicates the tool's function and scope, making it easy to parse and understand quickly.

  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 low complexity (1 parameter, no output schema, no annotations), the description is minimally adequate. It covers the basic purpose and parameter context but lacks details on behavioral traits, usage guidelines, and output format, which are important for effective tool invocation. It meets the minimum viable threshold but has clear gaps in completeness.

  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 description coverage is 100%, with the parameter 'period' fully documented in the schema (including enum values and description). The description adds minimal value by mentioning 'for a given period', which aligns with but does not expand beyond the schema. With high schema coverage, the baseline score of 3 is appropriate as the description does not enhance parameter understanding.

  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 with a specific verb ('Get') and resource ('PoT statistics'), listing the specific metrics returned (total swaps, turbo/full counts, turbo ratio) and the scope (for a given period). However, it does not explicitly differentiate from sibling tools like 'pot_query' or 'pot_stats', which might have overlapping functions, leaving some ambiguity about uniqueness.

  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 such as 'pot_query' or 'pot_health', nor does it mention any prerequisites, exclusions, or contextual cues for usage. It merely states what the tool does without indicating appropriate scenarios or comparisons to siblings.

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

• pot_healthB
  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 for behavioral disclosure. It mentions what gets checked (time source status, subgraph sync, server uptime, current mode) but doesn't disclose important behavioral traits like whether this is a read-only operation, if it requires authentication, potential rate limits, or what happens when the system is unhealthy. The description is functional but lacks critical operational context.

  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 core purpose ('Check PoT system health') followed by specific aspects being examined. Every word earns its place with no redundancy or unnecessary elaboration. Perfectly sized for this simple diagnostic tool.

  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 (no parameters, no output schema, no annotations), the description provides adequate context for what the tool does. However, it lacks information about the return format, error conditions, or what constitutes 'healthy' versus 'unhealthy' states. For a health check tool, knowing what the output looks like would be valuable, especially without an output schema.

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

  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 with specific verbs ('Check') and resources ('PoT system health'), listing the specific health aspects examined. It distinguishes from siblings by focusing on system health rather than generation, querying, statistics, or verification. However, it doesn't explicitly differentiate from 'pot_stats' which might also provide health-related statistics.

  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 its siblings. There's no mention of alternatives, prerequisites, or specific contexts where this health check is appropriate versus using other tools like 'pot_stats' for statistical monitoring or 'pot_verify' for validation checks.

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