state_snapshot

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

Without annotations, the description discloses the scope of state captured (symbol, timeframe, studies, drawings, visible range) and that it writes to a named file. However, it does not describe behavior when a snapshot with the same name exists (despite overwrite parameter in schema) or any potential errors.

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?

A single, focused sentence that is front-loaded with the action and lists included components without repetition.

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?

The description explains the tool's basic function and scope, but lacks a pointer to companion tools like state_restore and does not clarify the outcome when a snapshot already exists without overwrite.

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 100%, so the baseline is 3. The description adds context about what is captured but does not elaborate on the 'name' or 'overwrite' parameters beyond the schema.

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 uses a specific verb 'Capture' with a clear resource 'full chart state' and destination 'named snapshot file', listing included elements (symbol, timeframe, studies, drawings, visible range). This distinguishes it from siblings like state_restore and state_list.

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 explicit guidance on when to use this tool versus state_restore or state_list. The context is implied by the verb 'Capture', but there is no mention of alternatives or conditions.

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