blueprint_showcase

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

No annotations are provided, so the description carries the full behavioral burden. It implies a time-consuming rendering operation (the 'minutes in Blender' parenthetical) but does not state cost, duration, permissions, side effects, or whether outputs are written to disk or returned inline. It also does not clarify what happens if the gun has not completed the Gun Kit pipeline. The parenthetical about Blender time is a useful hint but insufficient for a tool with no annotation coverage.

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 long run-on sentence dense with visual element lists ('a title card, the source beside the copy, a turn round it, its clips (fire slowed, the reloads, the checks)'). It is not front-loaded with the core purpose and buries the actual output formats (GIF, MP4) at the end. The prose style prioritizes flavor over efficiency.

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 no output schema, no annotations, four parameters at 25% schema coverage, and a complex rendering pipeline, the description is inadequate. It does not specify the return value (file paths? URLs?), the required state of the gun, expected runtime, or how to handle errors. It leaves critical gaps an agent needs to invoke the tool 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 25% — only compare_figure has a schema description. The description mentions 'a title card' and 'the source beside the copy,' which loosely map to title and source_note/compare_figure parameters, but it does not explain what gun should be (a name? a path? an ID?) or what format title and source_note accept. With three undocumented parameters, the description does not compensate for the low coverage.

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 what the tool produces — a showcase render with a title card, source/copy comparison, turntable, and clips, output as GIF and MP4. However, it never states a clear verb+resource like 'renders a showcase video of a built gun' in a direct way, instead using a descriptive list of visual elements. An agent can infer it generates showcase media, but the phrasing is more evocative prose than precise function definition. It does distinguish itself from siblings like blueprint_page or gunkit_export by describing a unique multi-element video output.

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 explicit when-to-use guidance, no prerequisites stated (e.g., does the gun need to have been through Gun Kit first?), and no exclusions or alternatives named. The phrase 'has been through Gun Kit' implies a precondition but does not state it as a requirement. With many sibling tools related to blueprints and gunkit, the agent is left to infer when this tool is appropriate.

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