Server Quality Checklist

Tool Scores

• verify_certificateA
  3.7/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 discloses that the tool returns score, tier, hashes, Bitcoin anchor, and ledger status, but fails to mention whether it is read-only, has side effects, or any access constraints.

  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 relatively concise (two sentences) and front-loaded with the core action and result. The colon and list format is somewhat verbose but efficient.

  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 simple input (one required parameter) and no output schema, the description covers the essential purpose and output fields. However, it lacks details on output formatting, error conditions, or prerequisites.

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

  Parameters2/5

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

  The schema has one parameter (certificate_id) with 0% description coverage. The description does not elaborate on the parameter beyond the schema title 'Certificate Id', providing no additional semantic guidance for a required input.

  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 'Verify', the resource 'proof of authorship by certificate id', and lists returned fields (score, tier, hashes, Bitcoin anchor, ledger status). It distinguishes itself from siblings 'certify_creation' (creation) and 'get_agent_passport' (passport retrieval).

  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 explicitly states when to use: 'to confirm a creation was really timestamped and that it existed first.' It provides clear context but does not mention when not to use or alternative tools for other scenarios.

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

• get_agent_passportA
  4.2/5.0
  Behavior4/5

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

  With no annotations provided, the description carries full burden. It discloses the tool is a fetch operation and lists returned data, but does not mention authentication, failure modes, or potential 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?

  Single sentence with front-loaded verb 'Fetch'. Every part adds value: lists specific information returned. No wasted 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 a simple, single-parameter fetch tool with no output schema, the description covers the return content adequately. It lacks mention of edge cases or response format, but is sufficient for a straightforward read operation.

  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 0%, so description must compensate. The description adds context that the parameter identifies an agent, but does not specify format (e.g., did:key or handle). The parameter name 'did_or_handle' is self-explanatory.

  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 fetches an agent's public passport and enumerates its contents. It is distinct from siblings (certify_creation, verify_certificate) which handle different operations.

  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 usage for retrieving passport info, but does not explicitly state when to use this tool versus siblings or provide exclusions. However, the context from sibling names clarifies the boundary.

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

• certify_creationA
  4.7/5.0
  Behavior5/5

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

  No annotations are provided, so the description carries full burden. It thoroughly discloses the process: scores authorship (AAS 0-100), signs a C2PA manifest under the agent's sovereign key (tier 'signed'), timestamps (RFC 3161), and anchors to Bitcoin on a public immutable ledger. It also mentions it's free and lists return values (certificate id, authorship score, tier, verify URL).

  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 well-structured: a compelling tagline, then process explanation, usage guidance, and parameter list. Every sentence serves a purpose, though the 'Not a patent' sentence is somewhat tangential. It is not overly verbose, but a minor trim could improve conciseness.

  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 the tool has 5 parameters, no output schema, and no annotations, the description covers all necessary context: what the tool does, the role of each parameter, the outcome (return values), and usage context. It is complete for an agent to decide when to invoke this tool without additional information.

  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 description coverage is 0%, meaning no parameter descriptions in the schema. The description compensates fully with a dedicated 'Args' block that explains each parameter: prompt, output, handle, model, and tools. It clarifies what each represents (e.g., 'prompt: the task/instruction that produced the output'), adding critical meaning beyond the 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 opens with a clear, action-oriented statement: 'Prove you made it first: timestamp an AI creation and anchor it to Bitcoin.' It specifies the verb (timestamp/anchor), resource (AI creation), and the outcome (proof of authorship). It also distinguishes itself from sibling tools 'get_agent_passport' and 'verify_certificate' by being a creation certification tool, not a passport or verification tool.

  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 explicitly states when to use the tool: 'Use this whenever an agent makes something worth proving it made first.' It also clarifies that it's not a patent but verifiable priority/prior art, setting expectations. However, it does not explicitly mention when NOT to use it or compare with other tools, but given the siblings are different operations, the guidance is clear enough.

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