animation.nla_add_strip

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

The description only contributes risk and maturity metadata ("Risk: standard; maturity: L3") and a generic policy reminder. It does not disclose the behavioral effect of the command, any side effects, state mutations, or operational requirements. Annotations are all false and offer no safety profile, so the description carries the full burden and fails to meet it.

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 short, but this is under-specification rather than purposeful conciseness. It front-loads only identifying and policy boilerplate, with no functional information, so the brevity does not serve the agent.

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 parameter-heavy command with low schema coverage and no behavioral description, the definition is severely incomplete. It lacks operational meaning, parameter guidance, and any context about expected outcomes or side effects, despite having an output schema and numerous sibling tools to differentiate from.

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?

With schema description coverage at only 33% and 12 parameters, the description needed to compensate by explaining key fields like action, name, start, track, or objectId. It does not mention any parameter, leaving the agent to guess at semantics for most of the schema.

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 only states "PartMe Blender Harness command `animation.nla_add_strip`", which restates the tool name and title without saying what the command does. It never identifies the operation (adding an NLA strip) or the resource it affects, so an agent cannot determine the tool's purpose from the description alone.

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?

There is no guidance about when to use this tool versus alternatives such as blender_animation_insert_keyframe, blender_animation_action_list, or other animation tools. The generic note about per-request checks and session policy provides no decision-relevant context.

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