Server Quality Checklist

Tool Scores

• get_guideB
  3.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 clearly implies a read-only retrieval operation and names the available guide variants, but it does not disclose what the response contains, whether invalid guide names error, or any other runtime 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, tight sentence that front-loads the operation and immediately lists the valid options with clarifying parentheticals. Every part earns its place and no unnecessary wording is present.

  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 simple and the parameter is fully documented, so the basic invocation is clear. However, with no output schema and no annotations, the description could do more to explain the returned guide format or any relevant usage context for an agent.

  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 coverage is 100%, so the parameter is already documented. The description adds value beyond the schema by explaining what each guide covers: 'creating-nodes' is a custom node guide, 'quick-start' is an overview, and 'editor' is the visual editor.

  Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

  Purpose4/5

  Does the description clearly state what the tool does and how it differs from similar tools?

  The description clearly states the tool retrieves a jam-nodes guide and enumerates the specific available guides. It identifies the resource and the verb well, though it does not explicitly contrast itself with sibling tools like search_docs or get_api_reference.

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

  Usage Guidelines2/5

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

  No explicit guidance is given about when to use this tool versus the sibling alternatives. The description only implies its use for fetching one of the listed guides; there are no exclusions, prerequisites, or alternative routing.

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

• get_node_infoA
  3.6/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 of behavioral disclosure. The 'Get' verb implies a non-mutating read operation, which is the key behavioral trait here. However, it does not disclose what 'full documentation' actually contains (examples, parameters, return format) or what happens with an invalid/unknown type identifier. Adequate for a doc-lookup tool, 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?

  A single, tight sentence of about 20 words with no filler. The core action and resource are front-loaded, and the parenthetical examples illustrate the parameter without bloating the text. Every element 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?

  For a simple one-parameter lookup tool with no output schema and no nested objects, the description is nearly sufficient: it states the purpose, the required input, and gives concrete examples. The only real gap is that it never describes the shape of the returned 'full documentation' and says nothing about failure behavior for unknown type identifiers, but neither gap is critical for such a self-contained 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%, so the baseline is 3; the schema already defines 'type' as a node type identifier with examples. The description adds marginal value by providing an extra example ('filter') not present in the schema and by clarifying that the identifiers refer to built-in jam-nodes nodes. This is a slight enhancement, not a substantial one.

  Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

  Purpose4/5

  Does the description clearly state what the tool does and how it differs from similar tools?

  The description states a specific verb and resource: 'Get full documentation for a specific built-in jam-nodes node by its type identifier'. The phrase 'specific' and the examples ('http_request', 'conditional', 'filter') conceptually separate it from list_nodes and search_docs, though it never names siblings explicitly. Clear and unambiguous, but stops short of the explicit differentiation that earns a 5.

  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?

  Usage is implied rather than stated: the description signals this tool is for retrieving docs when you already have a node type identifier. However, there is no guidance about when NOT to use it or mention of alternatives such as list_nodes for discovering available types or search_docs for general queries, despite those siblings being visible in context.

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

• search_docsA
  3.8/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 of behavioral disclosure. It does state that the tool returns relevant sections rather than full documents, which is useful, but it does not describe result format, ordering, pagination, or any limitations. For a read-only search tool, this is adequate 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, efficient sentence that front-loads the action and resource before explaining the return value. Every word earns its place, and there is no redundant or vague phrasing.

  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 has low complexity (two simple parameters, no nested objects) and no output schema, but the description provides the general return shape ('relevant sections from all docs'), which is enough for an agent to invoke it correctly. Minor details like result structure or snippet format are not necessary 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 description coverage is 100%, so both parameters are already documented in the schema. The description adds no additional meaning about the query or maxResults parameters beyond what is already present, so the 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 states a specific verb ('Search'), a clear resource ('jam-nodes documentation'), and an explicit scope ('all docs (core API, nodes, editor, guides)'). It also identifies what it returns ('relevant sections'), making it easy to distinguish from sibling tools that retrieve specific node info, API references, or guides.

  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 searching across multiple documentation sources, but it does not explicitly contrast with alternatives like get_node_info or get_guide, nor does it state when not to use this tool. The scope is clear, but exclusionary guidance is missing.

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

• get_api_referenceA
  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 behavioral disclosure burden. It indicates the operation is a read-style lookup by saying 'Get', and it lists the accepted areas, but it does not describe the return format, content structure, or behavior on invalid area input. This is adequate but not richly transparent.

  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 tool's purpose and immediately follows with the necessary area values. There is no fluff or redundant restatement of the tool name.

  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 one-parameter tool with no output schema, the description provides the complete set of supported area values and clearly defines the lookup target. It could mention the returned reference format, but the core information needed to select and call the tool is present.

  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?

  The schema only says 'API area to look up' with no enum, so the description's explicit list of eight valid areas adds essential semantic value. This tells the agent exactly what values can be passed, which is the main parameter requirement.

  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 gets a jam-nodes API reference for a specific area and enumerates the valid areas. This distinguishes it from siblings like get_node_info, list_nodes, search_docs, and get_guide, which serve different doc/info retrieval needs.

  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 gives clear context: use this tool to look up API reference material for one of eight named areas. It does not explicitly state when not to use it or name alternatives, but the area list provides enough operational guidance for an agent to select it appropriately.

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

• list_nodesA
  4.3/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 behavioral burden. It transparently discloses the scope ('all 16 built-in nodes') and the returned fields (type, name, category, brief description), making the behavior predictable. It does not mention output format or ordering, but for a simple list tool this is a minor gap.

  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?

  A single sentence with no filler. It front-loads the action and scope, then lists the output fields. Every word 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 zero-parameter list tool with no output schema, the description is sufficient: it names the result set size, the population ('built-in'), and the fields returned. An agent can invoke this correctly without further information.

  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, so there is nothing for the description to clarify beyond what the empty schema already shows. The description instead usefully communicates what the response will contain, which is the relevant semantic information for this tool.

  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 ('List') and resource ('all 16 built-in jam-nodes nodes'), and names the exact fields returned. This clearly distinguishes it from sibling tools like search_docs and get_node_info, which serve different purposes.

  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 context is implied: use this tool to get an overview of all built-in jam-nodes nodes. However, there is no explicit guidance about when to prefer this over search_docs or get_node_info, and no exclusions are stated.

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