blender_render

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

Beyond the annotations, the description discloses the output contract: only validated relative paths and render statistics are returned, and still PNGs may additionally be delivered as MCP image content. It does not mention render cost or file overwrite behavior, but annotations already cover idempotency and non-destructiveness.

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?

Two sentences, no filler, with the core behavior and return contract front-loaded. Every clause adds useful information that is not already present in the annotations or schema.

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 sparse schema and no output schema, the description adequately covers output formats, destination root, and return value shape. It omits execution prerequisites and explicit file-writing side effects, but for a two-parameter render tool the essential guidance is present.

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?

The schema has 0% description coverage, so the description must compensate. It maps 'kind' to still PNG versus animation MP4 and ties 'path' to a relative location under CODEX3D_ARTIFACT_ROOT. It does not explicitly state the expected file extension or whether path refers to the output file, but the meaning is reasonably inferable.

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 specific verb ('Render'), the target resource ('Blender scene'), and the exact output formats ('PNG' and 'MP4'), plus the artifact root. This clearly separates blender_render from sibling tools like blender_inspect_scene or blender_create_snapshot.

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 purpose implies when to use it—when a still or animation render is needed—but there is no explicit when-not-to-use guidance or mention of alternatives. The sibling tool list is not leveraged to route the agent away from similar tools.

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