Server Quality Checklist

Tool Scores

• claude_codeA
  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 behavioral disclosure burden. It honestly describes the agent's autonomous capabilities (read/write files, run shell commands), implying potential side effects. However, it does not disclose safety constraints, permission requirements, or destructive potential beyond what is implied.

  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: the first states purpose and capabilities, the second explains return value and follow-up mechanism. Every sentence adds value, no redundancy, and key information is front-loaded.

  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?

  While the tool has many parameters and no output schema, the description covers the essential outcome (result text + session_id) and follow-up usage. For a complex tool, it provides sufficient context, though more detail on return format or behavior with various parameters could 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%, meaning all 13 parameters have descriptions in the schema. The description does not add additional parameter semantics beyond what the schema already provides. 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 the tool sends tasks to an autonomous Claude Code agent and lists specific capabilities (reads/writes files, runs shell commands, searches codebases). It distinguishes from sibling tools by noting it returns a session_id for follow-ups via claude_code_reply.

  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 implicitly provides usage guidelines by stating return of session_id for follow-ups, indicating when to use this tool (initial task) vs claude_code_reply (follow-up). No explicit when-not or alternatives, but context is clear.

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

• claude_code_replyA
  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 burden. It indicates state continuation but does not disclose behaviors like session validity, error handling, or whether the operation is safe. This is adequate but not comprehensive.

  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, no fluff, front-loaded with purpose. Every sentence earns its place.

  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 7 parameters, no annotations, and no output schema, the description covers the essential purpose and usage. It could be more complete about return values or limitations, but it is sufficient for a continuation 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 coverage is 100%, so the schema already documents all parameters. The description adds minimal extra context (e.g., 'from a prior claude_code response'). 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 it continues a previous claude_code conversation using session ID, and explicitly differentiates from siblings by focusing on follow-ups and iterative refinement.

  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 says to use for follow-up questions and multi-step workflows, providing clear context. It does not explicitly state when not to use, but the sibling names imply that.

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

• claude_code_transcriptA
  4/5.0
  Behavior3/5

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

  With no annotations, description carries the full burden. It discloses that the tool returns chronological user/assistant messages (a read operation) but does not mention authentication requirements, rate limits, or error handling for invalid session_ids.

  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?

  Extremely concise: two sentences, front-loaded with the primary purpose, no redundant words. Every sentence adds essential context.

  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?

  Provides sufficient context for a transcript retrieval tool: what it returns and how to get session_id. Lacks mention of pagination behavior or error handling, but given the schema parameters, it is mostly complete.

  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?

  Input schema has 100% description coverage, with each parameter clearly described (e.g., session_id, limit, offset, include_system). The description adds no new semantic information beyond the schema, meeting the baseline for high coverage.

  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?

  Description clearly states the verb 'retrieve' and the resource 'full conversation transcript', specifying it returns chronological user/assistant messages. It is distinct from siblings like 'claude_code_reply' and 'claude_code_timeline'.

  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 advises using session_id from a prior query or timeline lookup, providing clear context for when to use this tool. However, it does not mention when not to use it or alternative tools beyond the implicit distinction.

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

• claude_code_timelineA
  4.1/5.0
  Behavior3/5

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

  No annotations provided. Description does not explicitly state whether the tool is read-only, destructive, or any auth requirements. It implies read-only behavior by describing queries, but doesn't guarantee it.

  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 that front-load the purpose and action, with no unnecessary words. Every part adds value.

  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?

  No output schema; description does not specify the format of returned data (e.g., fields in timeline entries). Lacks details on pagination, limits, or error handling, but sufficient for basic 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 coverage is 100% with parameter descriptions. The description adds some context (e.g., 'agent sequence' for run_id) but does not significantly improve understanding 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?

  Description clearly states 'Query the cross-agent workflow timeline' which is a specific verb and resource. It distinguishes from sibling tools like claude_code_transcript which handles full transcripts.

  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?

  Provides explicit guidance on when to use each argument: 'No args: list all runs. run_id: show one run's agent sequence. session_id: retrieve timeline entry and session metadata.' Also directs to alternative tool: 'Use claude_code_transcript for full transcripts.'

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

• claude_code_reportA
  4.4/5.0
  Behavior4/5

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

  Discloses what the tool produces: HTML report, content of detailed report, cost breakdown, transcripts. Notes dependency for include_transcripts. No annotations exist, so description carries full burden; it does well without contradictions.

  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: one states purpose, second covers both parameter modes and output handling. No redundancy, perfectly front-loaded.

  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?

  No output schema, but description explains return value (HTML string) and what to do with it. Covers both parameter use cases sufficiently for a simple two-parameter tool.

  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?

  Schema description coverage is 100% (baseline 3). Description adds value by elaborating on report contents for run_id and explaining the default for include_transcripts.

  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?

  Clearly states it generates self-contained HTML reports of workflow runs. Distinguishes two modes: without run_id lists all runs; with run_id provides detailed report including agent sequence, cost breakdown, and collapsible transcripts. Distinct from sibling tools like claude_code_reply or claude_code_transcript.

  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 describes when to use each parameter: omit run_id to list, provide it for detailed report. Mentions prerequisite for include_transcripts (session persistence). No explicit when-not-to-use, but the two modes are clearly differentiated.

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