Create pose ControlNet driver

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

The description discloses that it renders a TOP (consistent with readOnlyHint=false), uses GPU rasterization, and optionally auto-wires to senders. This adds value beyond the annotations, which only indicate non-destructive and open-world behavior.

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, concise paragraph that front-loads the main action and packs all essential information without redundancy. Every sentence adds value.

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 the tool's complexity (15 parameters, no output schema) and rich annotations, the description provides a complete understanding of its role, output, and integration with ControlNet and external senders. No major gaps.

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 100%, so the schema already fully documents each parameter. The tool description does not add parameter-specific details, but it provides overall context. A score of 3 is appropriate as per guidelines.

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 clearly states the tool's action ('Render a canonical OpenPose-colored stick figure TOP') and the resource (from a pose CHOP). It differentiates from siblings like `create_pose_tracking` by specifying it's the driver that produces the conditioning image, not the tracker itself.

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 description implies usage context: 'from an existing pose CHOP produced by create_pose_tracking' and explicitly says 'No model inference — this tool produces the driver conditioning image that ControlNet consumes,' guiding when to use. It does not explicitly mention alternatives for visualization, but the context is clear enough.

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