Server Quality Checklist

Tool Scores

• get_sessionA
  4/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 that the tool returns 'full detail and current status', which implies read-only behavior, but does not specify side effects, error cases, or permissions. This is typical for a get operation but lacks deeper behavioral 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?

  Two sentences, front-loaded with action, then usage context. Every word earns its place, with no redundancy or unnecessary detail.

  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?

  The tool is simple (one parameter, no output schema, no annotations). The description sufficiently explains what it retrieves, when to use, and how the session ID is obtained. It does not detail return format, but the phrase 'full detail and current status' covers this adequately for a simple retrieval.

  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%: the parameter sessionId is described as 'Session id from create_session or list_sessions' in the schema. The description adds no extra parameter semantics beyond reinforcing the source of the ID, so 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 uses a specific verb ('Retrieve') and clearly defines the resource ('full detail and current status for ONE verification session'). It distinguishes from siblings by emphasizing 'ONE' session versus list_sessions, and references create_session/list_sessions for context.

  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?

  Explicitly states when to use: after create_session or after finding a sessionId via list_sessions, and the purpose: check progress/outcome. However, it does not explicitly mention when not to use or name alternatives, though the sibling tool names imply this.

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

• create_sessionA
  4.1/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. It discloses the expected output (sessionId, playerUrl, sessionStatus), the initial state (CREATED) and transition to RUNNING, and the PII constraint on subjectId. It does not cover error cases or authorization requirements, but the key behavioral traits are clearly described.

  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 at three sentences, but the third sentence has awkward grammar ('which is the link' could ambiguously refer to playerUrl or sessionStatus). It front-loads the core action and prerequisites, making it easy to scan. Minor redundancy exists but overall it is well-structured.

  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?

  Despite no output schema, the description explains the return values and the session lifecycle, which is essential for an AI agent to understand the tool's behavior. It also gives context about how to obtain the flowId. While it omits error handling and edge cases, the tool is relatively simple and the description is sufficient for correct 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 100%, and the description repeats the schema's parameter explanations (e.g., flowId from list_flows, subjectId as non-PII reference) without adding significant new detail. The locale parameter is not mentioned in the description, so the description does not augment the schema meaningfully. Baseline of 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 tool's purpose with a specific verb and resource: 'Create a new identity-verification session.' It also specifies the context (for a given flow) and differentiates from sibling tools (list_flows, list_sessions, get_session) by focusing on creation rather than listing or 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 provides clear context by indicating that flowId comes from list_flows and that subjectId is your internal reference, implying the prerequisite steps. However, it does not explicitly mention when not to use this tool or alternative options, so it earns a 4 rather than a 5.

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

• list_flowsA
  4.3/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 states the return values and its role as a prerequisite, but it does not explicitly disclose read-only behavior, authentication requirements, or potential edge cases like no flows returned. This is adequate for a simple list but lacks richer behavioral 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 three concise sentences with no filler: the action, the return fields, and the usage guidance. It is front-loaded with the core purpose and every sentence earns its place.

  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?

  For a simple list tool with no parameters and no output schema, the description is complete. It specifies exactly what is returned (id, name, description) and provides the key usage context (discover flowId first), covering all necessary aspects.

  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 (empty input schema), so there are no parameter details to clarify. Per the rubric, a baseline of 4 applies when there are no parameters, and the description correctly does not attempt to fabricate parameter semantics.

  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 'List' and the resource 'identity-verification flows' scoped to 'this IDnow account'. It specifies the return fields (id, name, description) and distinguishes it from session-related siblings by framing it as the discovery step for flowId.

  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 explicitly says 'Call this first to discover a flowId before creating or listing sessions', giving clear when-to-use guidance. It references the sibling session tools implicitly but does not name them explicitly or state when not to use it, so it lacks full alternatives specification.

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

• list_sessionsA
  4.7/5.0
  Behavior5/5

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

  With no annotations available, the description carries the full burden. It discloses several behaviors: newest-first ordering, automatic flow selection when flowId is omitted, and the specific return fields (sessionId, sessionStatus, outcome, createdAt) including all possible status values. This is far beyond a generic 'list sessions' statement.

  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 three sentences, each serving a distinct purpose: what it does, how it behaves, and when to use it. No redundant or extraneous information.

  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 output schema, the description effectively documents the return shape and statuses. It also covers ordering, fallback logic, and the next-step usage with get_session, making it complete for a simple list 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?

  Schema description coverage is 100% for both parameters. The description adds only a reiteration of the flowId fallback (already in the schema) and does not provide additional parameter-level insights. 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 'List verification sessions for a flow, newest first' – a specific verb and resource. It also explains the primary use case (finding a sessionId to pass to get_session), distinguishing it from sibling tools like list_flows and create_session.

  Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

  Usage Guidelines5/5

  Does the description explain when to use this tool, when not to, or what alternatives exist?

  Explicitly instructs when to use this tool: 'Use this to find the sessionId of a session you just created, then pass it to get_session for full detail.' It also notes the automatic fallback to the account's first flow when flowId is omitted, providing clear context for usage.

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