Server Quality Checklist

Tool Scores

• analyze_seriesA
  3.8/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 burden of behavioral disclosure. It explains the input format (points as sorted [timestamp, value] pairs) and the output shape (anomaly report with per-changepoint audit trail), and hints at budget constraints affecting the analysis. This goes beyond a mere restatement of the tool name, though it does not discuss side effects like budget deduction or error 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 compact and front-loaded with the core purpose, followed by a necessary input format detail and a clear statement of the return value. Every sentence adds useful information, and there is no filler or repetition of the tool name.

  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, lack of annotations, and absent output schema, the description covers the main function, the points format, and the return type, but it leaves important contextual gaps unexplained: what 'spend budget' means in concrete terms, how severity is determined, and the exact structure of the anomaly report. It is viable but not fully complete for an agent making correct invocation decisions.

  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?

  The schema description coverage is 0%, so the description must compensate for undocumented parameters. It explicitly explains the 'points' parameter and loosely ties 'metric' to 'fleet metric', but it provides no real semantics for 'tenant_id' or 'month', leaving two parameters underdocumented. This partial compensation is not sufficient for a four-parameter tool with no inline schema 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 uses a specific action phrase 'Detect changepoints in a fleet metric' and details what makes this tool distinct: explaining the most severe changepoints subject to a spend budget. It names the resource (fleet metric) and the expected output (anomaly report with audit trail), so an agent can understand the tool's core function without ambiguity.

  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 the tool is for changepoint detection within a cost-aware budget context, but it does not explicitly state when to choose this tool over alternatives or mention when not to use it. With no sibling tools listed, some of this pressure is relieved, but clear usage context such as prerequisites or complementary workflows is missing.

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