blueprint_to_gunkit

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

With no annotations, the description carries the full burden, and it does disclose that this runs in Blender and takes several minutes, plus the outputs it produces. However, it omits whether the operation overwrites existing rigs/clips, what auth or setup is required, and other side effects.

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 compact sentence that front-loads the step number and duration, which is efficient. But the telegraphic phrasing is cryptic and sacrifices clarity for brevity, making it less useful than a slightly fuller statement.

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?

Given no annotations, no output schema, and zero schema description coverage for two parameters, the description is too thin. It hints at the pipeline stage and duration but leaves parameter semantics, prerequisites, and behavioral safety details entirely unexplained.

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% for both parameters. The description does not explain what the required 'gun' argument should contain or what 'grip_steps' controls. It offers only the incidental phrase 'gun clips', which does not clarify the parameter's meaning or format.

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 a pipeline step and lists operations (rig, hand clips, gun clips, read-back), but it uses no clear verb and does not distinguish this from siblings like gunkit_build, gunkit_rig, or blueprint_build. An agent can infer it processes a built model through Gun Kit, but the exact action remains vague.

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?

The phrase 'Step 7' implies a position in a sequence, which gives some implied usage context, but it never states when to use this versus alternatives or what prerequisites must be met. No exclusions or alternative tool names are provided.

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