stocks_get_ema

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It does not mention data return format, pagination, rate limits, parameter effects, or any side effects. The one-sentence description provides no behavioral context beyond the basic operation.

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 concise sentence with no redundant words. It is front-loaded with the core purpose, and every word contributes to the meaning. This is appropriately sized for the minimal information conveyed.

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?

This is a complex technical tool with 8 parameters, no output schema, and no annotations. The one-sentence description is grossly insufficient for an agent to understand how to invoke it correctly, what parameters to set, or what response to expect. The high parameter count and lack of external documentation make this severely incomplete.

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 input schema has 8 parameters with 0% description coverage, and the description does not explain any of them. The only parameter referenced is 'symbol', which is already obvious from the schema and tool name. The description fails to add meaning for limit, window_size, series_type, timespan, or other parameters.

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 tool retrieves an Exponential Moving Average for a stock symbol, using a specific verb and identifying the resource. It distinguishes from sibling tools by specifying 'stock symbol', which differentiates it from forex, crypto, and options variants, though it lacks additional scope differentiation like date range or filtering.

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?

There is no guidance on when to use this tool versus alternatives like SMA or RSI, nor any mention of prerequisites or exclusions. The description merely states the action, leaving the agent without decision support for tool selection.

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