Server Quality Checklist

Tool Scores

• analyze_portfolioC
  2.9/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 only says 'analyze', loosely implying a read-only operation, but does not disclose output format, limitations, side effects, or any behavioral specifics. With 7 inputs and no output schema, this is a significant gap.

  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 one concise sentence, front-loading the verb and avoiding redundancy. It is efficiently structured, but the brevity sacrifices depth; however, the dimension rewards lack of fluff, so a moderately high score is appropriate.

  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?

  With 7 required parameters, no output schema, and no annotations, the description is insufficient. It does not clarify the nature of the analysis result, expected output structure, or any prerequisites/limitations. The description is too sparse for the tool's complexity.

  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 baseline is 3. The description adds a high-level framing ('investor profile and financial goals') but does not provide any additional param-specific meaning beyond what the schema already documents.

  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 uses a specific verb ('analyze') and resource ('investment portfolio'), and mentions the basis ('investor profile and financial goals'). It distinguishes from siblings like assess_risk (focused on risk) and simulate_investment (simulation), though 'analyze' is somewhat generic and doesn't specify the kind of analysis.

  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 explicit guidance on when to use this tool versus alternatives. There is no mention of exclusions or comparison to sibling tools like assess_risk or generate_report. The context is only implied through the phrase 'based on investor profile and financial goals', which is not enough.

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

• assess_riskB
  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 for behavioral disclosure. It states the analytical basis ('asset allocation and concentration') but does not mention whether this is a read-only operation, what the output format is, or any limitations such as requiring complete holdings. This leaves the agent under-informed about invocation 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 a single, front-loaded sentence with no redundant wording. It states the verb, object, and basis efficiently, which is appropriate for a tool with a single well-documented parameter.

  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?

  The schema is complete for the single parameter, but there is no output schema and no annotations, so the description must explain return values and behavior. It does not describe what the 'risk profile' output looks like or address the overlap with sibling tools, making it minimally adequate rather than fully complete.

  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 fully describes the 'holdings' parameter and its sub-fields with descriptions, so the baseline is 3. The description adds the concepts of 'asset allocation and concentration' as the analytical lens, but it does not explain how the input maps to these measures or provide further parameter-level detail.

  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 uses a specific verb ('Evaluate') and identifies a clear resource ('risk profile of an investment portfolio') with the basis of evaluation ('asset allocation and concentration'). It is clear and specific, but it does not differentiate from the sibling 'analyze_portfolio', which could overlap in purpose.

  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 explicit guidance on when to use this tool versus alternatives like 'analyze_portfolio' or 'simulate_investment'. The use case is only implied by the verb and inputs, with no exclusions or alternative references.

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

• get_market_insightsB
  3.1/5.0
  Behavior2/5

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

  With no annotations, the description carries the full burden. It indicates 'retrieve' implying a read-only operation, but it doesn't disclose any side effects, rate limits, response format, or data source. The description is minimal and doesn't enrich the agent's understanding beyond the basic action.

  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 a single, efficient sentence. It's front-loaded with the action verb and contains no unnecessary words. Every word earns its place.

  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?

  The tool is relatively simple with two optional parameters and no output schema. The description gives a basic idea of what it does, but it doesn't explain the return structure or how the data might be used. Given the lack of annotations and output schema, the description could be more informative to enable 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 input schema already describes both parameters (limit and category) with 100% coverage. The description adds no additional meaning about how the parameters affect results, such as how category filters headlines or what limit controls. Since schema coverage is high, baseline 3 is appropriate.

  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 a specific action ('Retrieve') and resource ('latest market insights and financial headlines'). It distinguishes from sibling tools like analyze_portfolio or generate_report, which focus on analysis/reporting rather than retrieval. However, it doesn't explicitly differentiate itself, so it's not perfect.

  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 versus alternatives. It doesn't mention any prerequisites, exclusions, or scenarios where other tools would be more appropriate. The description simply states the function without context, leaving the agent to infer its use case.

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

• generate_reportB
  3.2/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 of disclosing behavioral traits. It mentions output formats but does not disclose side effects, required permissions, whether input data is mandatory, or any limitations. The description adds minimal behavioral context beyond the basic action.

  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 front-loaded, using a single sentence to state the tool's purpose and output formats. Every word is meaningful, with no redundant or filler content.

  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?

  The tool is moderately complex (4 parameters, 2 required, enums), but the description is sparse. There is no output schema or annotations, so the description should explain what the report contains, how 'data' is used, or what 'structured' means. It fails to provide this context, leaving significant gaps for the agent.

  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 baseline is 3. The description adds no additional meaning to parameters; it only mentions formats, which are already enumerated in the schema. The schema itself fully documents all parameters, so this score is appropriate.

  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 function: generating a structured wealth analysis report in PDF, JSON, or Markdown. This specific verb+resource combination distinguishes it from sibling analysis tools (e.g., analyze_portfolio, assess_risk), which focus on analysis rather than report generation.

  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. It does not mention prerequisites, exclusions, or the relationship to sibling tools. Users must infer that it is for report generation after analysis, but no explicit context is given.

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

• simulate_investmentB
  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 mentions 'deterministic financial calculations' but does not disclose what the output format is (e.g., future value, schedule), any underlying assumptions (e.g., compounding frequency), or limitations. This is a significant gap for a simulation tool.

  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 a single sentence that is appropriately concise and front-loaded with the verb 'Simulate'. It avoids repetition of schema details and contains no unnecessary words.

  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 a well-documented schema, the description fails to provide essential context about the tool's output or behavior. There is no output schema, and the description does not mention what the simulation returns (e.g., final corpus, year-wise breakdown) or any edge cases. For a non-trivial financial tool, this is incomplete.

  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 input schema provides complete descriptions for all parameters (100% coverage), so the baseline is 3. The description adds no additional meaning beyond referencing 'SIP or lump-sum', which maps to monthlySIP and initialInvestment already documented in the schema. It does not enrich parameter understanding.

  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 function with a specific verb ('Simulate') and resource ('the growth of SIP or lump-sum investments'). It distinguishes itself from siblings like analyze_portfolio and assess_risk by focusing on simulation rather than analysis or risk assessment.

  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 simulating investment growth but does not explicitly state when to use it versus alternatives or when not to use it. No exclusions or comparisons to sibling tools are provided, leaving usage guidance at an implied level.

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