sam2_propagate_mask

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

With no annotations provided, the description carries the full burden for behavioral disclosure. It reveals that propagation is approximate and driven by sampled inside/outside points, but it does not disclose side effects, prerequisites, output behavior, or whether the operation is read-only or mutating.

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 a single sentence with no filler, but the phrasing is cryptic and compresses essential meaning at the expense of clarity. It is concise rather than well-structured.

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 tool with five parameters, no schema descriptions, and no output schema, this is too sparse: the input/output contract, optional parameters, and expected result are absent. Only someone already familiar with SAM2 tooling could call this correctly.

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 only loosely relates mask to an 'initial mask' and inside/outside point sampling. It does not explain input, output, blur, or erosion, leaving even required parameters semantically 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?

The description names the operation ('propagation'), the model ('SAM2'), and a distinctive detail ('from inside/outside points sampled in the initial mask'), which helps distinguish it from sibling segmentation and refinement tools. It is still terse and does not explicitly state what the propagated output is or whether it applies across video frames.

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 guidance is provided on when to choose this tool over alternatives like sam2_object_track, sam2_refine_mask, or sam2_video_inpaint. The word 'approximate' hints at a quality tradeoff, but no conditions or alternatives are mentioned.

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