analyze_ema_snapshot

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

No annotations are provided, so the description carries the full burden. It discloses that only the latest value is returned, which is a key behavioral constraint. But it does not mention idempotency, data source, authentication, or potential side effects.

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 concise with two sentences and a warning. It front-loads the purpose and provides critical usage guidance without unnecessary fluff. Every sentence adds value.

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 has 4 parameters, no output schema, and many siblings, the description provides a fair overview of purpose and a key usage warning. However, lack of parameter semantics and output format details leaves gaps for the agent to properly invoke the tool.

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%, so the description should compensate. It only discusses the 'periods' parameter via default values. No explanation is given for 'pair', 'type', or 'limit'. This is insufficient for the agent to use parameters correctly without external knowledge.

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 returns EMA latest values, alignment, crosses, and slope with default periods. It distinguishes from chart drawing via prepare_chart_data, but does not explicitly differentiate from other snapshot tools like analyze_sma_snapshot.

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 ⚠️ warning explicitly states when not to use (for chart drawing, use prepare_chart_data). However, it lacks guidance on when to use this tool versus other snapshot analysis tools among siblings.

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