analyze_sma_snapshot

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

With no annotations, the description carries the full burden. It clearly states that only latest values are provided ('最新値のみ') and points to the charting tool for historical data. It does not disclose side effects (none expected) but covers the key constraint.

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 relatively short but mixes Japanese and English, includes an emoji, and lacks clear structure. It is not overly verbose, but could be more organized.

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 4 parameters and no output schema, the description is incomplete. It mentions snapshot elements but does not define cross detection parameters or alignment states. It also omits default behaviors and error conditions.

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%, and the description does not explain any of the four parameters (pair, type, limit, periods). The only indirect mention is in the charting hint referencing 'SMA_25, SMA_75', but no explicit parameter semantics are provided.

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 explicitly states that the tool provides a snapshot of SMA values, cross detection (golden/dead cross), and alignment state. This clearly distinguishes it from siblings like analyze_ema_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 description indicates that for time series chart drawing, one should use prepare_chart_data, providing a clear exclusion. However, it does not compare against other snapshot tools or suggest when to use this over alternatives.

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