blender_silhouette_compare

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

With no annotations provided, the description carries the burden of behavioral disclosure. It tells the agent the output type (difference score and overlay image) and the general behavior (render silhouette and compare), which is helpful. However, it does not disclose what file formats the difference score/overlay come in, whether the overlay is saved to disk or returned as base64, whether the object must be visible/selected, or whether this writes any files to the filesystem.

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?

One sentence, front-loaded with the verb and resource, followed by the output types and the purpose. Every element earns its place; no filler or redundant restating of the tool name.

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 four-parameter tool with a fully documented schema, the description names the output and purpose, which covers most of what an agent needs to invoke it. The main gap is the return format of the overlay image and where the difference score is delivered, but the purpose and output types are sufficiently clear for initial selection and invocation.

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 documents all four parameters clearly. The description names the key components (object, reference image, silhouette comparison) but does not add significant meaning beyond the schema, such as how camera_angle affects the silhouette comparison or what resolution implies for the difference score. Baseline 3 is appropriate.

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 a specific verb ('Render object silhouette') and resource ('compare against a reference image'), with a clear output ('difference score and overlay image') and purpose ('proportion verification'). Among the large sibling list, there is no other tool doing silhouette comparison; it stands out from render-only tools (blender_render_image, blender_render_multi_angle) and measurement tools.

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 clearly implies usage for proportion verification, but it does not explicitly state when to use it instead of alternatives like blender_render_image, blender_render_multi_angle, blender_measure, or blender_calibrate_from_reference. No when-not-to-use conditions or alternative tool names are given. The purpose sentence gives adequate context for an agent to infer the right time to call it.

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