set_pose_sequence

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

Goes well beyond the annotations (which only say write/destructive/high safety risk) by disclosing transaction semantics: patches merge with pre-transaction state, failure triggers restoration, unverified recovery locks further writes, no timeline extension, and a read-back requirement after timeout. This is unusually rich behavioral context for a mutation tool.

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?

Dense but front-loaded: the core action leads, followed by transactional guarantees. Sentences are terse and mostly earn their place, though the failure/recovery clause is packed and could be split.

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 complex, destructive, 0%-documented three-param tool with no output schema, the transaction/safety story is complete but the parameter and return-value story is not. An agent still lacks guidance on constructing the poses payload.

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 0% and the tool has 3 required nested parameters. The description only vaguely maps to 'frames' (the 1-8 / maxItems limit on poses) and 'semantic Point targets'; it says nothing about scene_id or character_id formats nor the head/chest/pelvis pose structure the schema expects, so it fails to compensate for the coverage gap.

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 states a specific verb and resource: 'Write 1-8 unique existing frames of semantic Point targets.' This distinguishes it from singular siblings like set_semantic_pose and frame-offset siblings like offset_semantic_pose_sequence, though it never names them explicitly.

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?

It implies batch usage ('1-8 unique existing frames in ONE ... call') and the transactional context, but gives no explicit when-to-use or when-to-prefer-alternatives guidance relative to set_semantic_pose or offset_semantic_pose_sequence.

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