Server Quality Checklist

Tool Scores

• get_agent_automationB
  3.3/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 full burden. It only mentions a cost of $0.01 USDC, which is a behavioral trait, but does not disclose any other side effects, permissions, or limitations.

  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 sentences, no redundant information. The action and resource are front-loaded. Every word contributes value.

  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?

  For a simple getter with one parameter and no output schema, the description is basic but adequate. It conveys what is returned and the cost. However, it could mention that the slug must be known or that this is for exact retrieval, especially given sibling search tools.

  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 100% as the only parameter 'slug' is described with an example. The description adds no additional meaning beyond the schema, so baseline of 3 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 verb 'Get' and the specific resource 'full agent automation prompt and workflow steps by slug'. It distinguishes from sibling tools like search_agent_automations and list_automation_categories.

  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 lacks guidance on when to use this tool versus alternatives. No exclusions, prerequisites, or context are provided. The only extra info is the cost, which does not help with usage decisions.

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

• list_automation_categoriesA
  3.7/5.0
  Behavior2/5

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

  With no annotations, description only states listing and cost. No disclosure of safety (read-only), rate limits, pagination, or output behavior. Basic with significant gaps.

  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 sentences, front-loaded with purpose and key detail (35 categories, counts, cost). No unnecessary words.

  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?

  Despite no parameters and low complexity, lacks explanation of what 'counts' means (e.g., count of automations per category) and output format minimal for a listing tool.

  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?

  No parameters present (schema coverage 100% trivially). Description adds no parameter info since none exist, but per guidelines baseline is 4 for zero-parameter tools.

  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?

  Description clearly states 'List all 35 automation categories with counts', providing a specific verb (list), resource (automation categories), and quantitative detail (35 with counts). This distinguishes it from sibling tools like search_agent_automations.

  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?

  Includes cost ($0.005 USDC) as usage context but lacks explicit when-to-use, when-not-to-use, or comparisons with siblings. Usage is implied as a simple listing operation.

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

• review_signal_anomalyA
  3.9/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 lists returned fields and includes a cost disclaimer ($0.07 USDC), which is helpful. However, it does not explicitly state if the tool is read-only or if there are side effects. Since it is a scoring function, the lack of explicit read-only hint is a minor gap.

  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 three sentences long, with the first sentence stating the core purpose, the second listing return values, and the third adding legal and cost information. It is front-loaded and every sentence adds value.

  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?

  No output schema exists, so the description must cover return values. While it lists return fields (anomaly_score, anomaly_level, etc.), it does not explain their types or structure (e.g., what are 'drivers' or 'component scores'?). Also, the 'features' parameter is a complex nested object with many possible keys; the description provides no guidance beyond the schema examples.

  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 minimal additional meaning beyond the schema, only summarizing the parameters. It does not clarify the format or allowed values for the 'features' nested object, which is a complex parameter.

  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 what the tool does: 'Score a market signal feature set for unusual conditions before downstream analysis.' It specifies the verb (score), resource (market signal feature set), and context (before downstream analysis). It distinguishes from sibling tools like get_crypto_risk or get_crypto_signals by focusing on anomaly detection in feature sets.

  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 when to use ('before downstream analysis') but does not explicitly state when not to use it or provide alternatives among sibling tools. No comparison with tools like audit_trade_decision or check_trade_preflight, which are closely related.

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

• check_trade_preflightA
  4/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 full burden. It discloses the cost ($0.05 USDC) and what checks are performed, but does not mention idempotency, failure behavior, or side effects.

  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 front-loaded purpose, zero wasted words. Cost information is efficiently integrated.

  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?

  The description covers key aspects for a preflight check tool, but lacks details on return values or output structure given no output schema. Otherwise complete for its 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 coverage is 100%, and the description adds no significant meaning beyond the schema's descriptions. The listed symbol values and affiliate ID explanation are already present in the schema.

  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 defines the tool as 'Step 1 of the auditable decision loop' and lists specific checks (market state, cooldown, data freshness, model context), distinguishing it from siblings like get_crypto_decision.

  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?

  The description explicitly positions the tool as the first step before calling get_crypto_decision, providing clear usage context. However, it does not exclude alternative tools or state when not to use it.

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

• search_agent_automationsA
  4/5.0
  Behavior4/5

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

  No annotations provided, so description carries full burden. It adds value by disclosing the monetary cost ($0.01 USDC) and return fields. However, it omits whether the operation is read-only and if there are any side effects or rate limits.

  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 sentences with no wasted words: first states purpose, second lists returns and cost. Front-loaded with the key action and scope.

  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?

  Covers purpose, return fields, and cost. Lacks details on pagination behavior beyond the limit parameter, ordering, or error handling, but sufficient for a straightforward search tool.

  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 100% with clear descriptions for both parameters. Description adds minimal extra context (e.g., 'keyword' example) but does not significantly enhance understanding beyond the schema.

  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 it searches automation prompts by keyword and specifies return fields (title, description, complexity, services). It distinguishes from sibling tools like get_agent_automation (single automation) and list_automation_categories (categories).

  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?

  Usage is implied for keyword-based searches, but no explicit guidance on when to use vs. alternatives like get_agent_automation for a specific automation, nor any when-not-to-use conditions.

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

• get_crypto_signalsA
  4.1/5.0
  Behavior3/5

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

  With no annotations, the description carries full burden. It discloses cost ($0.05 USDC) and that outputs are supporting context. However, it lacks details on authentication, rate limits, or response structure. Simple tool but incomplete transparency.

  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 sentences, each essential: first states the tool's core output, second adds usage caveat and cost. No filler, perfectly front-loaded.

  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?

  Lacks output schema, and description is vague about exact output fields ('directional values', 'Kronos model context'). Doesn't explain 'audit record' or 'calibrated range' references. Adequate for a simple tool but incomplete for rich output.

  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 coverage is 100% for the single optional parameter. The description adds meaning by explaining the affiliate ID's purpose ('affiliate earns commission') and cost implication, going beyond the schema's basic description.

  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 provides 'Latest Kronos model context for BTC, ETH, SOL, XRP, ADA,' specifying a verb and resource with explicit asset list. It distinguishes from siblings like get_crypto_decision by emphasizing 'supporting context, not standalone trade instructions.'

  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?

  The description explicitly says to use directional values 'with the calibrated range, risk state, and audit record,' providing integration guidance. It does not explicitly exclude alternatives, but the context is clear enough for an agent to decide when to use this tool.

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

• audit_trade_decisionA
  4.2/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. It discloses the monetary cost ($0.07 USDC) and the return format (direction, PnL%, verdicts). However, it does not specify whether the operation is read-only, what happens if the decision_id is invalid, or any 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 is extremely concise—two sentences and a brief verdict list. Every word adds value: purpose, cost, return types. No 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?

  Given no output schema, the description adequately covers return values (direction, PnL%, verdicts). It also mentions cost as a contextual factor. However, it lacks details on error handling or what happens when the decision_id doesn't exist, which would be helpful for completeness.

  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 100%, but the description adds valuable context: decision_id is a 'UUID from a previous get_crypto_decision call', window has a default and options, affiliate_id is optional with cost clarification. This enhances understanding beyond the parameter 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 clearly states the tool's purpose: 'Verify a Kronos decision_id against later market prices.' It uses a specific verb ('verify') and resource ('decision_id') and distinguishes from siblings like get_crypto_decision by focusing on post-hoc verification.

  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 phrase 'The accountability step' implies usage after a decision is made, but no explicit when-to-use or when-not-to-use guidance is provided. Alternatives (e.g., get_crypto_decision) are not mentioned, and there are no exclusions or prerequisites.

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

• get_crypto_decisionA
  4.2/5.0
  Behavior4/5

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

  With no annotations, the description carries the burden. It discloses a monetary cost ($0.15 USDC) and implies a creation side effect. It does not explicitly state idempotency or side effects beyond journal entry creation, but the cost disclosure adds significant transparency.

  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 four concise sentences, each adding distinct value: purpose, return fields, follow-up action, and cost. No wasted words, effectively front-loaded.

  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 2-parameter tool with no output schema and no annotations, the description covers purpose, behaviors (cost, creation), and a usage hint. It lacks explanation of 'Kronos context' and does not differentiate explicitly from siblings, but overall it is reasonably complete.

  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 coverage is 100%, providing basic parameter info. The description adds value by explaining the affiliate_id's commission mechanism ('no extra cost to you'). This extra semantic detail justifies a score above baseline.

  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 creates a market-intelligence journal entry and lists the return fields. It distinguishes itself from siblings like get_crypto_signals or get_crypto_risk by focusing on creating an entry with a decision ID for later auditing.

  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 instructs to call audit_trade_decision after the evaluation window, providing some guidance on follow-up. However, it lacks explicit direction on when to use this tool vs siblings like check_trade_preflight or get_crypto_signals.

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

• get_crypto_signal_historyA
  4.2/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. It discloses important behavioral details: costs '$0.05 USDC' and specifies the data covers 'recent' history for five assets. It does not mention read-only status or rate limits, but the non-destructive nature is implied.

  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, using two sentences to convey purpose, usage, and cost. It is front-loaded with the key information about what the tool provides.

  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?

  Given no output schema, the description could elaborate on return format or fields, but it covers the essentials: asset list, timeframe ('recent'), and cost. It is sufficient for a simple history-fetching tool with clear input parameters.

  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 does not add extra meaning beyond what the schema provides for 'hours' and 'affiliate_id'. The schema already explains both parameters adequately.

  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 provides 'Recent Kronos context history' for specific assets (BTC/ETH/SOL/XRP/ADA) and the action is to 'inspect model context and freshness'. It distinguishes itself from siblings like get_crypto_signals and get_crypto_decision by focusing on historical context.

  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?

  The description gives explicit usage guidance: 'Use it to inspect model context and freshness before or after a decision.' It implies the context of decision-making but does not explicitly state when not to use it or mention alternative tools.

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

• get_crypto_forecastA
  4.4/5.0
  Behavior4/5

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

  No annotations exist, so the description carries full burden. It discloses the calibrated nature ('honest 80% prediction interval'), the cost, and that directional bias is supporting context. It could mention rate limits or authentication, but for a forecast tool, it is sufficiently transparent about 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?

  Every sentence is informative and no wasted words. The description is front-loaded with the key output type and then expands on specifics. It earns its space efficiently.

  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?

  With no output schema, the description adequately describes return values (range_80, point return, upside probability) and the empirical coverage. It omits error conditions or authentication details, but for a simple read-like tool with optional parameters, it is largely complete.

  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 covers both parameters 100%. Description adds value beyond schema by explaining the cost, the calibrated interval, and that affiliate_id earns commission without extra cost. This enriches the meaning of the parameters for the agent.

  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 specific verbs and resources: 'Conformally-calibrated price forecast' and lists exact outputs (80% prediction interval, point return, upside probability). It clearly distinguishes from sibling tools like get_crypto_signals and get_crypto_decision by emphasizing the calibrated range and cost.

  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?

  Provides clear context: directional bias is supporting but the calibrated range is the validated product, and costs $0.05 USDC. While it doesn't explicitly state when NOT to use it or name alternatives, it implies suitability for probabilistic price forecasting versus other signal or decision tools.

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

• get_crypto_riskA
  4.4/5.0
  Behavior3/5

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

  Discloses the financial cost of $0.02 USDC, which is a key behavioral trait in the absence of annotations. However, it does not explain what 'cooldown context' means or any potential side effects, leaving some ambiguity.

  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 front-load the purpose and usage guidance. Every sentence provides value without unnecessary 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?

  Given the tool has no parameters and no output schema, the description covers the key aspects: what it returns (risk state and cooldown context), cost, and usage context. Missing details like authentication or rate limits are not critical for a context-only tool.

  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?

  No parameters exist, so the input schema provides 100% coverage. The description does not need to add parameter semantics, and the baseline score of 4 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?

  Describes the tool as providing 'current market risk state and cooldown context' for Kronos decisions, clearly distinguishing it from sibling tools like get_crypto_decision or get_crypto_forecast. The description explicitly states it is 'not a standalone trading command,' reinforcing its specific role.

  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?

  Explicitly states the tool is 'useful as supporting context, not a standalone trading command,' providing clear guidance on when to use it. Also mentions the cost ($0.02 USDC), helping the agent decide if it's worth invoking.

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