study_template_save

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

Goes beyond the annotations: it discloses that the write targets a native account (consistent with openWorldHint) and that the tool performs independent content readback verification after writing. The concurrency guard (exact prior content hash required for replacement) is valuable behavioral context not expressed anywhere in the schema or annotations.

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 core action front-loaded and the safety constraint second. The compression leaves a couple of phrases ('independent content readback', 'exact prior content hash') dense but not wasteful.

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?

For a non-idempotent, open-world write with no output schema, the description covers the write target and the overwrite guard but omits the boolean save scope flags, what verification failure looks like, and any permission/account requirements. Adequate for the happy path, thin for edge cases.

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 only 29%, so the description must compensate more, and it only partially does: 'Replacement' maps to replace_id and 'content hash' maps to expected_content_sha256. The save_symbol and save_timeframe toggles, which control what portions of the study config are captured, are never mentioned anywhere and remain opaque.

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?

Specific verb+resource+destination: saves the active study configuration as a native account template, which implicitly distinguishes it from sibling snapshot/export tools that produce local artifacts. It does not name those siblings outright, so differentiation relies on the agent knowing the family.

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?

'Replacement requires exact prior content hash' gives a real precondition for the overwrite path, but the description never says when to choose this over study_template_snapshot, study_template_export, or layout_save, nor does it state prerequisites such as having an active chart with studies loaded.

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