sentiment

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

With no annotations provided, the description carries full burden but only states basic function. It does not disclose potential rate limits from alternative.me, authentication needs, or behavior for missing data. The example only shows a parameter usage.

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 short but contains unnecessary repetition (the same sentence appears twice). The example is helpful. Removing the duplication would improve conciseness without losing content.

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 simple tool with one optional parameter and no output schema, the description covers the input well but omits details about the response format (e.g., what 'current reading' and 'history' look like). It is adequate but not complete.

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 schema already describes the 'limit' parameter with default and max, achieving 100% coverage. The description adds value by providing a concrete example (limit=7) that aids understanding of how to request history.

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 identifies the tool as providing the Crypto Fear & Greed Index from alternative.me, with current reading and optional history. The verb 'get' is implied, and the resource is distinct from siblings like 'momentum_score' or 'volatility'.

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 usage for crypto sentiment queries but does not provide explicit when-to-use or when-not-to-use guidance. No alternatives are named, and usage context is only implied by the example.

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