Server Quality Checklist

Tool Scores

• get_market_featuresA
  4.4/5.0
  Behavior4/5

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

  With no annotations, the description carries the full transparency burden. It discloses success and error return shapes ({ticker, as_of, features} or {error: reason}) and specifies failure conditions ('unsupported ticker' or fetch failure). It does not mention side effects or permissions, but as a read-only 'fetch and compute' operation, this is acceptably complete.

  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 tightly structured in five sentences. It front-loads the core action, then adds example, return format, error case, and workflow order. Every sentence contributes useful detail without 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?

  For a simple one-parameter tool with an output schema, the description covers all essential context: what it does, argument format via examples, return structure, error behavior, and its role in the two-step process with get_forex_signal. It leaves feature names to the output schema, which is appropriate.

  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 0%, so the description must compensate for the bare parameter definition. It provides two concrete ticker examples ('EURUSD=X', 'GBPUSD=X') and implies a Yahoo Finance format, but does not fully define the valid pattern or enumerate supported pairs. This is partial compensation, leaving some ambiguity about acceptable inputs.

  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 opens with 'Fetch and compute the feature vector for a forex pair,' which is a specific verb+resource combination. It clearly distinguishes from sibling tool get_forex_signal by stating 'Call this first, inspect the features, then pass them to get_forex_signal,' establishing a unique role in the workflow.

  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?

  Explicit guidance: 'Call this first, inspect the features, then pass them to get_forex_signal.' This provides an explicit sequence relative to the sibling and tells the agent exactly when to use this tool. It lacks explicit 'when-not' scenarios, but the workflow instruction is strong enough to warrant full credit.

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

• get_forex_signalA
  4.5/5.0
  Behavior4/5

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

  No annotations are provided, so the description carries the full burden. It discloses both success and error return formats, including conditions for missing features or unsupported tickers. It does not discuss side effects or permissions, but for a model inference tool these are less critical.

  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 concise and well-structured: a one-sentence action summary, a short parameter list, and a clear return/error specification. Every sentence adds value with no redundancy.

  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 the tool's modest complexity, an output schema, and two parameters, the description covers the invocation flow completely: prerequisite (get_market_features), parameter semantics, success return shape, and error conditions. This is sufficient for an agent to call the tool correctly.

  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 0%, but the description compensates by specifying example ticker values and defining features as the dict returned by get_market_features. It does not enumerate all possible tickers or the internal structure of features, but it provides essential linkage to the upstream 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 action: 'Run the XGBoost model' to generate a forex signal from pre-computed features. It clearly distinguishes itself from the sibling tool get_market_features by positioning itself as the consumer of those features.

  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?

  It explicitly states that features must come from get_market_features, establishing a clear prerequisite and usage context. It does not list when not to use the tool or alternatives, but with only one sibling the guidance is sufficient.

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