Server Quality Checklist

Tool Scores

• get_freshnessC
  2.9/5.0
  Behavior3/5

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

  Discloses that coverage is not full-market and bounded, adding context beyond the name. However, lacks mention of read-only nature, authentication requirements, or error behavior. Annotations are absent, so description carries full burden but falls short.

  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 concise sentences with no fluff. First sentence delivers primary purpose, second adds important caveats. Efficient and well-structured.

  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 no output schema, description does not describe return format or example output. Also missing parameter guidance. Only covers purpose and a single caveat, leaving significant gaps for agent decision-making.

  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% and description does not mention the single parameter (freshness_window_hours). No additional meaning provided beyond what the schema already states.

  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 it returns freshness status for a specific universe (Headless Records watched ticker universe) and distinguishes from siblings by focusing on coverage status rather than insider activity or filing provenance.

  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 (assess_insider_activity, get_filing_provenance). No explicit usage conditions or 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.

• get_filing_provenanceB
  3.1/5.0
  Behavior3/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 states the tool summarizes 'public SEC filing data provenance', implying a read-only operation. It includes a disclaimer about not providing investment advice. However, it does not explicitly declare read-only status, rate limits, or authentication requirements.

  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 consists of two sentences with no redundancy. The first sentence provides the core purpose, and the second adds a necessary disclaimer. Every word serves a purpose.

  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 absence of annotations, output schema, and parameter descriptions, the description is incomplete. It mentions return fields (URL, timestamp, hash) but does not address error handling, format, or how the parameter is used. The agent may not be able to reliably invoke the tool.

  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?

  The input schema has one required string parameter 'accession_number' with minLength 1, but the description does not explain its meaning, format, or how it relates to provenance. With 0% schema description coverage, the description should clarify the parameter, but it fails to do so.

  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 verb 'Return' and the resource 'source provenance for an imported SEC Form 4 filing'. It specifies what is included (URL, timestamp, hash). It distinguishes from siblings like 'assess_insider_activity' and 'get_freshness' by focusing on provenance.

  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 the sibling tools. It does not mention prerequisites, constraints, or specific contexts. The agent would need to infer usage from the tool name and sibling names.

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

• assess_insider_activityB
  3.3/5.0
  Behavior4/5

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

  With no annotations, the description provides substantive behavioral disclosure: it is 'deterministic,' 'non-advisory,' and explicitly states what it does NOT provide (buy, sell, hold, etc.). It mentions coverage limitations. This goes well beyond basic transparency, though it could add details on error handling or data freshness.

  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 two sentences with no filler. The first sentence front-loads the core purpose, and the second sentence effectively clarifies limitations. Every word serves a purpose, achieving high conciseness.

  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?

  Despite the clear purpose, the description lacks completeness: no output schema exists, and the summary format is not described. The three parameters are left unexplained, and there is no guidance on parameter interactions or expected behavior. Important context about the 'bounded' coverage is vague.

  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?

  The description does not explain any of the three parameters (ticker, period, freshness_window_hours). Schema coverage is 0%, and the description adds no meaning beyond the input schema. For example, it doesn't describe how 'period' affects the summary or what 'freshness_window_hours' controls.

  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 returns a 'deterministic, non-advisory summary of reported public SEC Form 4 insider activity for a ticker.' It specifies the resource (insider activity) and verb (return summary), and distinguishes from investment advice. However, it does not explicitly differentiate from sibling tools, though they appear unrelated.

  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 for SEC Form 4 insider activity but does not provide explicit guidance on when to use versus alternatives. It notes that the tool uses 'bounded watched-ticker and imported-filing coverage' and does not offer recommendations, which partially clarifies scope. No direct when-not or sibling comparisons are given.

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