stocks_get_sma

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

With no annotations provided, the description carries the full burden of disclosing behavioral traits, but it provides none. It does not mention what the returned data looks like, how parameters like window_size or timespan affect results, or any limitations, making the tool behaviorally opaque.

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 short sentence, which is concise, but it is under-specified rather than appropriately structured. It lacks any organization or additional sections to clarify the tool's behavior, especially given the complexity of 8 parameters.

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 complexity (8 parameters, no output schema, no annotations), the description is grossly incomplete. It provides no information about return values, parameter interactions, or potential side effects, making it insufficient for reliable invocation.

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 has 0% description coverage, yet the description only mentions 'stock symbol' without elaborating on any of the other 7 parameters such as limit, order, timespan, or window_size. It adds minimal meaning beyond the schema and fails to compensate for the lack of parameter documentation.

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 operation as retrieving a Simple Moving Average for a stock symbol, which is specific and understandable. However, it does not differentiate this tool from siblings like stocks_get_ema or forex_get_sma, so the purpose is clear but not fully contextualized.

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 such as EMA or RSI. The description lacks any indication of appropriate use cases, prerequisites, or exclusions, leaving the agent without 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.