indicator_ema

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

No annotations provided. The description only mentions a data requirement but does not disclose if the tool is read-only, side effects, or authorization needs. For a stateless calculation, readonly is implied but not stated.

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?

Extremely concise: two short sentences, no filler. The key purpose and constraint are front-loaded. Perfect for a simple tool.

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?

No output schema and no description of return values. For an indicator tool, agents need to know output format. Also lacks context on typical use cases or prerequisites beyond data count.

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 coverage is 100% with descriptions for both parameters (price array and period). The description adds a meaningful constraint: requires at least 'interval' data points, which is not enforced by schema (minItems is 1, but interval≥2 implies need for 2+ points).

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 calculates the Exponential Moving Average (EMA) using Chinese terms, which is specific. However, it does not distinguish from sibling moving average indicators like SMA or DEMA, making it less helpful for selection.

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 on when to use EMA over alternatives. The only usage hint is the data requirement (needs at least interval points), but no 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.