get_market_overview

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

With no annotations, the description carries the full burden. It clearly states what the tool returns: current BTC/ETH prices and Fear & Greed Index. It implies a read-only operation with no side effects, providing adequate transparency for a simple getter with zero parameters.

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, tight sentence that conveys all essential information without redundancy. Every word adds value, making it perfectly concise and well-structured.

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?

Given the tool's simplicity (no parameters, no output schema), the description is complete enough. It specifies the exact data returned and implies a one-shot call. It doesn't mention return format or limitations, but these are not necessary for such a basic tool.

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 schema is complete with 100% coverage. The baseline for 0 params is 4, and the description adds no param-specific detail because none is needed. It appropriately avoids inventing parameter semantics that don't exist.

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 clearly states the action ('Get') and specific resource ('crypto market overview') with concrete components (BTC/ETH prices and Fear & Greed Index). This unequivocally distinguishes it from siblings like get_public_digest and get_wallet_profile, which serve different purposes.

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 description implies the use case (when you need crypto market overview) but provides no explicit guidance on when to choose this tool over alternatives, nor any exclusions or prerequisites. Sibling names suggest distinct purposes, but no direct comparison is given.

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