Server Quality Checklist

Tool Scores

• get_signal_statsC
  2.9/5.0
  Behavior2/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. It states the tool retrieves statistics (implying read-only behavior) but doesn't cover critical aspects like authentication requirements, rate limits, error handling, or response format. This leaves significant gaps for a tool that likely accesses sensitive trading data.

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

  Conciseness4/5

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

  The description is a single, efficient sentence that front-loads the core purpose. Every word contributes to understanding what the tool does, though it could be slightly more structured by separating purpose from metric examples.

  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?

  For a tool with no annotations and no output schema, the description is incomplete. It doesn't explain what the returned statistics look like (e.g., format, units), nor does it cover behavioral aspects like permissions or limitations. Given the complexity of trading data, this leaves too many unknowns for effective 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?

  The description adds no parameter-specific information beyond what's already in the schema (which has 100% coverage). It mentions 'strategy' and 'period' implicitly but doesn't explain semantics like what 'all' period means or how strategyId affects results. Baseline 3 is appropriate since the schema does the heavy lifting.

  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's purpose with specific verbs ('Get signal statistics and performance metrics') and resources ('for a strategy'), including key metrics like win rate, total trades, and P&L. It distinguishes from sibling tools by focusing on statistics rather than confirmation or raw signals, though it doesn't explicitly name alternatives.

  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?

  The description provides no guidance on when to use this tool versus its siblings (confirm_signal, get_trading_signals), nor does it mention prerequisites like authentication or rate limits. It implies usage for strategy analysis but lacks explicit context or exclusions.

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

• get_trading_signalsB
  3.1/5.0
  Behavior2/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 mentions 'real-time' and 'latest,' implying timeliness, but doesn't disclose behavioral traits such as rate limits, authentication needs, data freshness, or whether it's a read-only operation. For a tool with no annotations, this leaves significant gaps in understanding its 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 appropriately sized and front-loaded: the first sentence states the core purpose, and the second adds key details about returns. Every sentence earns its place by providing essential information without redundancy or fluff, making it efficient and well-structured.

  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?

  Given the tool's complexity (3 parameters, no output schema, no annotations), the description is moderately complete. It covers the purpose and return values but lacks details on behavioral aspects and usage context. Without annotations or output schema, more information on error handling or response format would improve completeness, but it's adequate for a basic read operation.

  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?

  The schema description coverage is 100%, so the schema already documents all parameters (strategyId, limit, status) with descriptions. The description adds no additional meaning beyond what the schema provides, such as explaining how filters interact or the significance of 'real-time' in parameter context. Baseline 3 is appropriate as the schema handles the heavy lifting.

  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's purpose: 'Get latest trading signals from live quantitative strategies.' It specifies the verb ('Get') and resource ('trading signals'), and mentions the source ('live quantitative strategies'). However, it doesn't explicitly differentiate from sibling tools like 'confirm_signal' or 'get_signal_stats,' which would be needed for a score of 5.

  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?

  The description provides no guidance on when to use this tool versus alternatives like 'confirm_signal' or 'get_signal_stats.' It mentions 'real-time BUY/SELL signals' but doesn't clarify if this is for monitoring, analysis, or other contexts. No explicit when/when-not instructions or prerequisites are included.

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

• confirm_signalB
  3.4/5.0
  Behavior2/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. It states that EXECUTE 'will trigger virtual trade execution' and SKIP 'will mark it as skipped', which covers basic outcomes. However, it omits critical details like whether this is a mutating operation (implied but not stated), permission requirements, side effects, or error handling, leaving significant gaps for a tool that likely modifies state.

  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 extremely concise and front-loaded, consisting of just two sentences that directly explain the tool's function and parameter meanings without any wasted words. Every sentence earns its place by clarifying purpose and usage, making it highly efficient.

  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?

  Given the tool's complexity (likely a state-modifying operation with financial implications), no annotations, and no output schema, the description is incomplete. It fails to address key aspects such as the nature of 'virtual trade execution' (e.g., simulated vs. real), confirmation consequences, error scenarios, or return values, leaving the agent with insufficient context for safe and effective 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 the schema already fully documents both parameters (signalId and decision with enum). The description adds minimal value beyond the schema by restating the enum meanings ('EXECUTE to trade, SKIP to ignore'), which is redundant. No additional context or constraints are provided, meeting the baseline for high schema 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?

  The description clearly states the tool's purpose with specific verbs ('confirm or skip') and resource ('pending trading signal'), distinguishing it from sibling tools like get_signal_stats and get_trading_signals which are read-only operations. It explicitly defines what happens for each decision option, making the purpose unambiguous.

  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 context by mentioning 'pending trading signal' and the two decision options, suggesting it should be used when a signal requires action. However, it lacks explicit guidance on when to choose EXECUTE vs. SKIP, prerequisites for use, or comparisons to alternatives, leaving some ambiguity for the agent.

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