Server Quality Checklist

Tool Scores

• anchorA
  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 carries the full burden. It discloses that it aggregates unanchored roots and submits to OTS calendars, which gives some behavioral context, but it does not mention side effects, reversibility, or result outcomes. No contradictions with annotations (none present).

  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 concise sentences that front-load the main purpose and process. No filler words.

  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?

  For a tool with one optional parameter and no output schema, the description explains the core action but omits the 'status' action (available in schema) and does not describe what is returned after submission. The absence of annotations and output schema means more was expected.

  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% and the only parameter 'action' is fully described in the schema with enum values and a default. The description adds no additional parameter detail beyond the schema, so baseline 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 uses specific verbs ('Request', 'Aggregates', 'submits') and clearly identifies the resource (Bitcoin anchor of pending ledger Merkle roots via OpenTimestamps). It distinguishes from sibling tools like audit, seal, verify by describing a distinct anchoring process.

  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 you want to anchor roots) but does not explicitly state when to use it over alternatives, nor does it mention exclusions. It doesn't reference the 'status' action available in the schema, providing only partial guidance.

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

• auditA
  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 behavioral disclosure burden. It does disclose the main checks performed (presence, integrity, Merkle continuity), which is helpful. However, it does not mention whether the operation is read-only, how errors or failures are reported, or what the output format looks like, leaving notable gaps for a tool with no annotation support.

  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 consists of two concise sentences that front-load the main purpose and then add relevant behavioral detail. Every sentence contributes meaningful information, with no redundancy or filler.

  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?

  With one parameter, no output schema, and no annotations, the description gives a good overview but lacks critical information about the return value or how audit results are reported. It says 'reports Merkle chain continuity' but does not specify the structure or success/failure semantics, making it incomplete for a tool that produces a non-obvious report.

  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 input schema already provides 100% coverage for the single 'receipts' parameter, including that it is an array of receipt objects in order. The description adds context about the audit being a chain and checking hashes, but does not provide additional parameter-level details beyond what the schema already states, 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 tool's function with a specific verb ('Audit') and resource ('chain of receipts against the APEX PSI ledger'), and elaborates on the scope by mentioning hash presence, integrity, and Merkle chain continuity. This distinguishes it from sibling tools like 'verify' and 'seal' by focusing on a multi-receipt chain audit rather than single operations.

  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 (auditing receipt chains against the ledger) but does not explicitly state when to prefer it over alternatives like 'verify' or 'seal'. It lacks explicit exclusions or alternative tool references, so usage guidance is only implied through the described purpose.

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

• sealA
  3.9/5.0
  Behavior4/5

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

  The description discloses key behavioral traits: it writes to an immutable ledger, uses SHA-256, Ed25519, and LMS-W4-SHA256 signatures. Since no annotations are provided, this context is essential for the agent to understand that this is a write operation with permanent effects. However, it does not mention output format or failure modes, which keeps it from a 5.

  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 the primary action. It efficiently describes the tool 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?

  The tool is a write operation with no output schema, but the description does not explain what the API returns (e.g., a receipt ID or hash). This is a gap for agent invocation. The description covers the core behavior but is incomplete regarding expected outcomes.

  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 input schema provides descriptions for all four parameters, so with 100% schema coverage the description adds no additional parameter-level meaning. The baseline of 3 is appropriate as the schema carries the full burden.

  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 'Stamp' and specifies the resource 'content', and it clearly differentiates from sibling tools (audit, verify, anchor, cite) by describing the cryptographic receipt and immutable ledger write. This is a specific action with clear scope.

  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 the use case (creating a cryptographic receipt) but does not explicitly state when to use this tool versus alternatives like verify or anchor. There is no mention of exclusions or when not to use it, so the usage is implied rather than explicit.

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

• verifyA
  3.9/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 the input types but not whether the operation is read-only, what the result means (e.g., found/not found), error behavior, 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 two sentences, front-loads the core action and ledger context, and avoids redundant detail or fluff.

  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?

  Input-side context is well covered by the description and schema, but the absence of an output schema means the agent still does not know what a successful verification returns (boolean, record, proof). The description is adequate for a simple tool but has a notable gap around outcomes.

  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 schema already documents both parameters at 100% coverage; the description adds the 'or' relationship and clarifies that one of the two inputs is expected, plus the connection to the seal tool's output. This is a modest but useful enrichment.

  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 a specific verb ('Verify') against a named resource (seal/APEX PSI immutable ledger) and identifies the counterpart to the seal tool. This clearly differentiates it from siblings like seal, audit, and cite.

  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?

  It establishes when to use the tool: after sealing, with either a receipt from the seal tool or a raw hash. It does not explicitly name alternatives or exclusions, but the context is clear enough for an agent.

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

• citeA
  4/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 convey behavior. It explains the output action (generating a citation) and the source (ledger entry), but does not disclose whether the operation is read-only, has side effects, or what happens with invalid input. This leaves some ambiguity around the tool's 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, 17-word sentence that gets straight to the point. Nothing is redundant; every clause contributes meaning.

  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 tool with no annotations and no output schema, the description covers the core purpose, input requirements, and allowed formats. It does not explicitly state the return value, but the title 'Generate citation' and the phrase 'Generate a citation' imply the output. This is adequate for a relatively simple tool.

  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 input schema fully describes both parameters (format with an enum and default, and receipt as an object from the seal tool). The description adds no additional detail beyond the schema, so it meets the baseline but doesn't enhance parameter understanding.

  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's function: generating a citation for a sealed receipt in specific formats (APA, BibTeX, MLA) and mentions the APEX PSI ledger entry. This distinguishes it from sibling tools like audit, seal, verify, and anchor, none of which are citation-related.

  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 defines the use case: it is for sealed receipts, which implies the user must have a sealed receipt (likely from the seal tool). It does not explicitly compare to alternatives or state when not to use it, but the context is clear enough for the listed siblings.

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