Server Quality Checklist

Tool Scores

• explore_spaceC
  2.3/5.0
  Behavior2/5

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

  No annotations provided, so description carries full burden. Does not disclose side effects, permissions, rate limits, or any behavioral traits. Only states 'explore', which is non-committal.

  Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

  Conciseness3/5

  Is the description appropriately sized, front-loaded, and free of redundancy?

  Short two sentences, but front-loading with vague phrase reduces impact. List of operations is useful but could be structured better. Minimal but not overly concise for the complexity.

  Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

  Completeness1/5

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

  With 12 parameters and 0% schema coverage, description is severely incomplete. No explanation of operations, their required parameters, or return values. Output schema exists but unmentioned.

  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?

  Schema description coverage is 0%, so description must add meaning. It only lists operation names without explaining any parameter. Parameters like x, y, face, etc. are not described, leaving agent guessing.

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

  Purpose3/5

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

  The verb 'explore' is vague and 'philosophical manifold' is abstract, but listing operations gives some idea. Not a tautology, but doesn't clearly state concrete purpose. Distinguishes from sibling tools implicitly via domain, but lacks explicit differentiation.

  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 guidance on when to use this tool vs alternatives. Does not suggest scenarios or mention sibling tools. The list of operations implies different behaviors, but no context for selection.

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

• extend_schemaC
  2.7/5.0
  Behavior3/5

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

  Notes automatic contradiction detection, which is a behavioral trait. However, with no annotations, the description should disclose more about side effects, reversibility, and required permissions; it only provides one behavioral insight.

  Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

  Conciseness3/5

  Is the description appropriately sized, front-loaded, and free of redundancy?

  Two sentences plus a list of operations make it concise, but it lacks structure and omits important details; every sentence is functional but incomplete.

  Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

  Completeness2/5

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

  With 12 parameters and no parameter descriptions, the tool is complex. The description does not explain return values (output schema exists) or how to use parameters, leaving significant gaps.

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

  Parameters1/5

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

  Schema coverage is 0%, yet the description does not explain any of the 12 parameters (e.g., face, x, y, tags, strength). Users must infer meanings from names alone, which is insufficient.

  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?

  Description clearly states 'Add constructs or relations to the graph' and lists two operations (add_construct, add_relation). It distinguishes the tool's action from siblings like create_prompt_basis, explore_space, interpret_basis, but doesn't explicitly contrast them.

  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 guidance on when to use this tool versus alternatives. Only mentions available operations without context on prerequisites or exclusions.

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

• create_prompt_basisA
  4.5/5.0
  Behavior4/5

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

  With no annotations, the description bears full burden. It outlines output modes (default, compact, focused) with approximate sizes, and describes the coordinate structure. It does not mention side effects, permissions, or rate limits, but as a read-like creation tool, the disclosure is adequate.

  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?

  Three short paragraphs (about 100 words) that are front-loaded with the main purpose, followed by usage and output details. Every sentence adds value, no redundancy or fluff.

  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 0 required params, 4 optional params, and an output schema, the description covers input options and output modes well. It could briefly name the 12 dimensions, but the output schema likely details that. Overall, sufficient for an AI agent.

  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 coverage is 0%, so the description fully compensates. It explains that 'intent' is natural language, 'coordinate' is a JSON object with 12 faces (x, y, weight), and that compact/focused control output verbosity. This adds crucial meaning absent from 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 clearly states the tool measures intent across 12 philosophical dimensions and returns a construction basis. It uses specific verbs ('measure', 'return') and a clear resource, and distinguishes itself from siblings by focusing on basis creation for dimensional precision.

  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 advises using this tool before constructing prompts where dimensional precision, coherence, or completeness matters. It also explains input options (intent or coordinate) and output modes, but does not directly compare to sibling tools or state when not to use.

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

• interpret_basisA
  4.5/5.0
  Behavior4/5

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

  No annotations provided, but the description details the tool's behavior: extracts the guidance section and formats it as readable text with dominant dimensions, gaps, and strongest resonance. This goes beyond a simple 'interpret' to specify output content.

  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?

  Three sentences, front-loaded with purpose, no wasted words. Each sentence adds value.

  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 one parameter with no schema coverage, the description fully explains the parameter and behavior. Output schema exists, so return value details are not needed. The tool is simple and well-described.

  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 only parameter 'basis' has no schema description, but the description compensates by specifying it expects 'JSON output from create_prompt_basis', adding essential meaning to the raw type string.

  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 'interpret' and the resource 'construction basis produced by create_prompt_basis', effectively differentiating it from sibling tools like create_prompt_basis (which produces the basis).

  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?

  Description implies usage context: takes JSON output from create_prompt_basis. While it doesn't explicitly state when not to use alternatives, the dependency on a prior tool output is clear.

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