Server Quality Checklist

Tool Scores

• memo_getA
  3.9/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. 'Retrieve' implies a non-mutating read operation, but it does not disclose behavior for missing IDs, return format, or any side effects. It provides basic context but lacks richer safety guarantees.

  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 verb and resource, with no redundant information. It earns its place and is easy to parse.

  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 simple retrieval tool with one parameter, the description covers the core purpose but omits details about the return structure or error behavior (e.g., what happens if the ID is not found). The lack of an output schema makes this a notable gap, though the tool's simplicity mitigates it somewhat.

  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 already covers the sole parameter 'id' with a description and example, so schema coverage is 100%. The tool description's phrase 'by its ID' merely restates what the schema provides, adding no additional semantic meaning.

  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 the specific verb 'Retrieve' with the resource 'previously saved conversation context' and specifies the identifier ('by its ID'). This clearly distinguishes it from siblings memo_list (lists all), memo_set (creates/updates), and memo_delete (removes).

  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 when a specific memo ID is known, but it does not explicitly state when not to use it or mention alternatives like memo_list for enumerating all memos. The context is clear but lacks explicit exclusionary guidance.

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

• memo_deleteA
  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 carries the behavioral burden. It states the action (delete) but does not disclose consequences like irreversibility, permissions, or error handling. The behavior is largely implied by 'delete', but lacks additional context that would be valuable.

  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, front-loaded sentence with no wasted words. It immediately communicates the verb, resource, and parameter, making it highly scannable and efficient.

  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 simple delete tool with one fully documented parameter and no output schema, the description is complete enough. It does not mention return values or error conditions, but these are not required given the tool's simplicity. A note about irreversibility would improve 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% with a clear parameter description ('The memo ID to delete'). The description's 'by its ID' adds nothing beyond the schema. Baseline 3 is appropriate as the schema already fully documents the parameter.

  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 'Delete' with a clear resource 'saved memo' and identifies the key parameter 'by its ID'. It fully distinguishes from sibling tools (memo_get, memo_list, memo_set) which perform 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 the tool is for deleting a specific memo, which is distinct from the sibling tools. It doesn't state explicit alternatives or when-not-to-use, but the context is clear enough for a simple CRUD operation; no misleading guidance.

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

• memo_listA
  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 burden of behavioral disclosure. It adds the useful context that expired memos are excluded, but it does not disclose any other behaviors such as return format, ordering, or error handling. This is acceptable for a simple list operation but not rich.

  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 sentence that is direct and front-loaded. It contains no fluff or redundancy, earning top marks for conciseness.

  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's simplicity (no parameters, no output schema), the description adequately covers the purpose and the expiration filter. It would benefit from mentioning what the list returns (e.g., full memo content vs. summaries), but overall it is sufficiently complete for a basic list operation.

  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, and the schema coverage is trivially 100%. The description does not need to explain parameters, and the baseline for 0-param tools is 4. No further elaboration is necessary.

  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 ('all saved memos'), with a specific scope ('haven't expired yet'). This distinguishes it from siblings like memo_get (single memo) and memo_set (write operation).

  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 usage is implied by the verb and resource, but there is no explicit guidance on when to choose this tool over memo_get, memo_set, or memo_delete. It does not mention any exclusions or prerequisites.

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

• memo_setA
  4/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 the tool returns a short ID for retrieval, which is useful behavioral information. However, it does not mention side effects, persistence, overwriting, or any prerequisites, leaving the agent with only a minimal understanding of the operation'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?

  Two sentences with no filler. The first sentence uses an imperative verb ('Save') and clearly states the purpose; the second explains the return value. Every word earns its place, 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.

  Completeness4/5

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

  The description explains the tool's purpose and return value, and the schema covers all parameters. Given the relative simplicity of the operation, it is reasonably complete. Missing are details about side effects or edge cases, but the essential context for using the tool is present.

  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 describes all six parameters with 100% coverage, so the baseline is 3. The description does not add any additional meaning to the parameters, but this is acceptable because the schema already provides the necessary details.

  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 action: 'Save the current conversation context' with a specific verb and resource. It distinguishes itself from siblings (memo_get, memo_list, memo_delete) by focusing on creation, and the context 'handoff to another session or agent' clarifies its unique role.

  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?

  Provides clear context for when to use: 'for handoff to another session or agent'. Does not explicitly mention alternatives or exclusions, but the purpose is sufficiently distinct from the sibling tools to imply appropriate usage. Lacks an explicit 'use this instead of memo_get' but the context is clear.

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