study_template_snapshot

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered; the description correctly avoids implying a write and adds that the capture is native rather than a saved-layout copy. However, it does not say whether the captured template is returned to the caller or held in session, which matters given idempotentHint=false implies repeated calls can diverge.

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?

Two tight sentences with the scope first and the disambiguation second; no filler and nothing an agent must read past to get the core action.

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?

There is no output schema, so the description must carry the return-value burden for a 'snapshot' tool, yet it never says what comes back or where the capture lands. Combined with the unaddressed relationship to study_template_save, an agent has enough to invoke it but not enough to predict the result.

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 coverage is 50%: target_id and expected_layout_id are self-documented, while save_symbol and save_timeframe are bare booleans. The phrase 'optionally including symbol/timeframe' maps exactly onto those two undocumented flags, adding real meaning beyond the schema. Only the default values remain unstated.

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?

A specific verb ('Capture') plus a concrete resource ('native template of the active chart's studies') with an explicit scope qualifier about symbol/timeframe. It distinguishes itself from layout_snapshot with 'This is not a saved-layout copy', but leaves the more relevant ambiguity unresolved: how it differs from sibling study_template_save, which an agent would likely consider first.

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 single line 'This is not a saved-layout copy' supplies a when-not, but there is no positive guidance on when to call this instead of study_template_save or study_template_get, and no statement of prerequisites such as a connected/active tab. Usage is only implied by the scope phrase.

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