flexsim_paint_meat

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

No annotations are provided, so the description carries the full burden and does so well: it discloses the session-persistence limitation of shapes in the .fsm, states that shape_name loading is idempotent, and specifies the timing constraint (after each reset+run). It omits auth/permission and error-handling behavior, but for a local FlexSim media operation this is strong disclosure.

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?

Purpose is front-loaded in the first line, followed by the scope condition, timing requirement, and Args/Returns blocks. Most sentences earn their place, though the verified-date note and repeated full STL path are minor excess.

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?

An output schema exists so return values need not be explained, yet the description still summarizes the JSON return shape. Combined with defaults, timing, and persistence caveats, an agent has enough to call it correctly; only auth/error semantics are unaddressed.

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%, so the description must compensate, and it does: it defines each of the four params (from_objects as source stations with default DesT1/T2/L3, file_path as the STL, shape_name as the media name, color_rgb as 0-1 channels). It even supplies a default for from_objects that the schema lacks, though it could state the exact color channel order.

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?

States a precise verb+resource ('Pinta como carne los items') and narrows scope to items already output from the named stations, distinguishing it from generic shape tools like flexsim_apply_shapes or flexsim_import_shape by specifying post-unboxing items in transit toward the picadora.

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?

Explicitly gives a when-to-use condition ('Correr tras cada reset+run') because the shape does not persist across sessions, and identifies the target population (post-desencajado items in Pie*/BeltDT*/picadora queues). It does not, however, name sibling alternatives or when NOT to use it.

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