trigger_part_render

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

No annotations are provided, so the description carries the full burden. It discloses that renders are generated from parametric templates without supplier assets and that matching uses category, package, and MPN suffix. However, it omits details like the queueing nature of the job, idempotency (implied by 'force' parameter), and potential errors.

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 consists of three sentences, each providing distinct and essential information: main action, generation process, and input requirement. No unnecessary words or repetition.

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 existence of an output schema (not shown) and 4 parameters, the description is mostly complete. It explains the core workflow and input requirements. However, it does not mention the asynchronous nature of rendering or how to check the resulting job status, which a sibling tool ('check_render_status') covers.

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 100%, so baseline is 3. The description adds value beyond the schema by explaining the matching logic (based on category, package, MPN suffix), which helps understand how template_override might be used. It does not add extra syntax details.

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 verb 'queue' and the resource 'Blender render job for an electronic component'. It distinguishes from siblings like 'render_schematic' by specifying that it deals with component renders from parametric templates, not schematics.

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 provides clear context on when to use this tool (to generate a render of a component) and mentions input conditions ('Pass either sku or part_id'). It does not explicitly state when not to use or mention alternatives, but the context is sufficient.

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