Server Quality Checklist

Tool Scores

• get_patternA
  4.3/5.0
  Behavior3/5

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

  No annotations exist, so the description carries the burden. It discloses the tool returns pattern text but does not mention behavior on invalid pattern names, error handling, or whether the result is cached. For a read-only retrieval tool, this is adequate but could be improved.

  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 unnecessary words. Front-loaded with the action and immediately clarifies usage. Every sentence serves a purpose.

  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?

  With only one simple parameter, no output schema, and no complex behavior, the description fully covers what the agent needs—return value, source of names, and when to use it.

  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 covers 100% of parameter description including example. The description adds 'by name (see list_patterns)' which ties the parameter to the sibling tool but no additional semantic detail 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?

  The description clearly states it returns the full text of an orchestration pattern by name, and references list_patterns, distinguishing the tool from its sibling. The verb 'return' and resource 'pattern' are specific.

  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 says to use this tool to apply the pattern when orchestrating ask_gpt calls, and mentions list_patterns for obtaining names, giving clear when-to-use and alternative reference.

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

• ask_gptA
  4.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 must carry the full burden. It mentions that higher reasoning_effort is deeper but slower, and that models have different capabilities (e.g., max effort per model). However, it fails to disclose potential behavioral traits such as token limits, cost implications, or timeout 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 dense but every sentence adds value. It front-loads the core purpose, then provides clear guidelines and examples. No redundant or filler content.

  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 absence of an output schema, the description does not explain what the tool returns (e.g., plain text response). It covers usage patterns well but lacks details on error handling or maximum response size. Still, it provides sufficient context for an AI agent to use correctly with the sibling tools.

  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% (all parameters have descriptions), so baseline is 3. The description adds significant value by explaining model aliases and use cases (sol for reasoning, terra for coding, luna for high-volume), the reasoning_effort scale with model-specific caps, and how to write instructions. This goes beyond the schema's minimal descriptions.

  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: 'Ask an OpenAI model as an expert subagent. ONE tool for everything.' It specifies the key parameters (model, instructions, reasoning_effort) and distinguishes from sibling tools (list_patterns, get_pattern) by noting they are for patterns, not LLM calls.

  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 extensive guidance: when to use fast models (gpt-5.6-luna) for high-volume work, strong models (gpt-5.6-sol) for reasoning, different reasoning_effort levels, and the orchestration patterns (worker vs two-layer-cross-model-expert). Explicitly recommends calling list_patterns/get_pattern first for non-trivial work.

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

• list_patternsA
  4.7/5.0
  Behavior4/5

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

  No annotations provided, but the description discloses the return structure (name, title, summary, when to use). It doesn't mention potential side effects or access requirements, but for a read-only list operation this is sufficient.

  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 purpose and usage, no fluff. Every 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 zero parameters and no output schema, the description fully covers what the tool does, what it returns, and when to use it in relation to sibling tools.

  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?

  No parameters exist; baseline score is 4 since the description does not need to compensate for any missing param info.

  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 lists orchestration patterns for driving ask_gpt, and distinguishes from siblings by mentioning get_pattern as the next step and ask_gpt as the consumer.

  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 says when to call: before non-trivial expert work like reviews, audits, threat modeling, and large-document analysis. Provides workflow: call this, then read the chosen pattern with get_pattern.

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