get_crypto_risk

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

With no annotations, the description carries the burden of behavioral disclosure. It discloses the cost ($0.02 USDC) and the nature of the data returned. It does not mention rate limits or error conditions, but for a read-only retrieval with a cost, this is reasonably transparent.

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

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

The description is a single, front-loaded sentence with no fluff. It states the action, the resource, the timing, and the cost in a compact form.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a no-parameter read tool with no output schema, the description adequately explains what the user will receive (risk state, signal streaks, cooldown context). It could add more detail on how to interpret 'risk state' but is sufficient for a pre-analysis check.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool has zero parameters, so the description needs no parameter explanations. Baseline for 0 params is 4, and the description appropriately focuses on the tool's output and cost.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses a specific verb 'Retrieve' and clearly identifies the resource: 'current market risk state, signal streaks, and cooldown context'. It also notes the timing ('before deeper analysis'), distinguishing it from deeper analysis tools 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.

Does the description explain when to use this tool, when not to, or what alternatives exist?

The phrase 'before deeper analysis' explicitly indicates when to use this tool, providing clear context. However, it does not explicitly mention alternatives or when not to use it, leaving some ambiguity relative to sibling tools like get_crypto_preflight.

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