get_history_sentiment

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

The description only states the basic function without disclosing behavioral traits such as data format, required parameters beyond symbol, or any destructive or read-only nature. No annotations are provided to supplement.

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?

While the description is concise (one sentence), it is under-specified, omitting critical information. It is not efficiently structured for an agent to act upon without additional context.

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 lack of annotations, output schema, and detailed parameter descriptions, the one-sentence description is far from complete. An agent would lack understanding of the return format, required inputs, and behavioral semantics.

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?

Schema description coverage is 0%, yet the description only mentions 'symbol' implicitly. The 'days' parameter is unexplained, leaving the agent to guess its meaning (likely a time range).

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 it provides a 'historical sentiment series for a symbol,' which is a specific verb-resource combination. However, it does not differentiate from siblings like get_sentiment or get_social_pulse, which could overlap.

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?

No guidance is provided on when to use this tool versus alternatives (e.g., get_sentiment for current data). The description lacks any when-to-use or when-not-to-use context.

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