ViperMesh for Blender

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

With no annotations, the description carries the full burden. It discloses that the tool performs a Blender connectivity check and returns context plus suggested follow-up calls, but says nothing about failure behavior, latency, or whether the check is side-effect free.

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 short sentences, front-loaded with the invocation rule and followed by the return content. No filler or repetition 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 an orchestration tool with no output schema and no annotations, the description should sketch the shape of the returned context. "Compact operating context" and "recommended next calls" gesture at it but leave the agent guessing what fields arrive.

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 tool takes zero parameters, so there is no parameter semantics to explain; the baseline for a parameterless tool applies. Nothing in the description muddies that.

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?

States a specific action and scope: it checks Blender and returns operating context plus recommended next calls for one persistent session. That distinguishes it reasonably from check_blender_connection, though it never names that sibling explicitly.

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?

"Call once at session start" gives clear when-to-use guidance and implies the once-per-session constraint. It stops short of naming alternatives or stating when not to call it (e.g., mid-session refreshes).

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

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

With no annotations at all, the description carries the full behavioral burden, yet it discloses nothing beyond the word "approved." It does not say what happens with an unapproved name, whether executed commands can modify or destroy data in the scene, whether an active session is required, or how failures are reported — all essential for an arbitrary dispatcher.

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 single front-loaded sentence contains no filler, but its brevity comes at the cost of under-specification rather than efficiency; one or two more sentences about command discovery and params would earn their place.

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 generic dispatcher with a free-form nested params object, zero annotations and no output schema, the definition is far too thin — it omits discovery workflow, side-effect profile, and error behavior that an agent needs before invoking arbitrary scene commands.

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 0% for both parameters, so the description must compensate and does not. It never explains that "name" must match an entry from list_blender_tools, nor that "params" is validated against that command's own signature — a serious gap given the untyped nested object.

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 gives a verb and resource ("Call one approved ViperMesh Blender command") and the word "one" faintly distinguishes it from call_blender_tool_batch, but it never explains what a "command" is or where valid command names come from (presumably list_blender_tools). An agent still cannot tell from the description alone how this differs from run_blender_scene_stage or the batch sibling.

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 guidance on when to use this tool versus call_blender_tool_batch or run_blender_scene_stage, and no mention of prerequisites such as establishing a session or discovering approved command names first. Usage is only inferable from the name.

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

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

With no annotations at all, the description carries the full behavioral burden. It does add real context — execution is ordered, bounded, and runs in one persistent session against 'approved' commands — but it says nothing about error handling (the stopOnError parameter is never mentioned), whether side effects from earlier commands persist after a failure, or what the call returns. Those are material gaps for a tool that mutates a scene.

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 tight sentences with zero filler; the core operation is front-loaded and the usage constraint follows immediately. Nothing is repeated from the schema or the title.

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?

There is no output schema and no annotations, and the description does not cover return values, per-command results, or failure behavior. For a batch execution tool with an undocumented stopOnError flag, the definition is too thin to let an agent invoke it confidently in error-sensitive situations.

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 0% across two parameters, so the description must compensate and does not. 'Ordered bounded' hints at array ordering and the 32-item cap, but stopOnError is never explained and the name/params shape of each command entry is left entirely to the schema. An agent gets no guidance on what the second parameter actually does.

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?

States a specific verb and resource: 'Run an ordered bounded sequence of approved ViperMesh Blender commands through one persistent session.' The notions of ordering, boundedness and a single persistent session separate it from a single-command tool. It stops short of naming call_blender_tool as the non-batch counterpart, so the sibling distinction is implied rather than stated.

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?

'Use only when intermediate observations are not needed to choose the next command' is a genuine selection criterion that tells the agent when this tool is appropriate and, by implication, when the single-command sibling is. There is no explicit exclusion for error-sensitive sequences or a named alternative, which keeps it below a 5.

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

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

With no annotations, the description carries the full behavioral burden. It usefully discloses that the probe is local and loopback-socket based, implying a cheap, side-effect-free read, but it does not say how non-responsiveness is surfaced (error vs. boolean), whether there is a timeout, or what the caller should do next.

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?

A single front-loaded sentence with no filler. The resource and scope (local, loopback) come first, and nothing is repeated from the title.

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 zero-parameter connectivity probe with no output schema, the definition covers what is being checked and where. The remaining gap is the shape of the result on failure, which matters slightly more here than for a typical read tool since the outcome is the entire product.

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 tool takes zero parameters, so the baseline of 4 applies. The description correctly implies the target socket is configuration-driven rather than a caller-supplied argument, which matches the empty input schema.

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 and resource: checking whether the ViperMesh Blender addon responds, scoped to a configured loopback socket. That is enough to separate it from siblings such as call_blender_tool or list_blender_tools, which act on the addon rather than merely probing it. It stops short of an explicit sibling contrast, so a 4 rather than a 5.

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?

Usage is only implied: an agent can infer this is a pre-flight connectivity probe to run before invoking other Blender tools. There is no explicit when-to-use statement, no guidance on what to do after a failure (e.g., run bootstrap_vipermesh_session), and no named alternative.

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

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

No annotations exist, so the description carries the full burden. 'Read' plus 'approved' and 'checked-in' communicates that this is a safe, read-only lookup against a curated bundle rather than arbitrary filesystem access. It does not disclose behavior on an unknown filename, path handling, or the shape/size of the returned document.

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 short, front-loaded sentence with no filler; the resource and scope are established immediately. It is arguably too terse for the disclosure burden it carries, but nothing is wasted.

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 simple single-parameter lookup with no output schema and no annotations, the definition covers what the tool fetches but not what comes back (raw Markdown text) or how failures surface. An agent could call it, but could not predict the response or error handling.

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 single 'filename' parameter has zero schema description coverage, so the schema supplies only a 1-255 character string constraint. The description implies it names a Markdown reference in the skill bundle, but adds no format guidance (extension, relative path, case sensitivity) or examples to compensate for the coverage gap.

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?

States a concrete verb and resource: 'Read one approved Markdown reference from the checked-in ViperMesh agent skill.' That is specific enough to distinguish it from siblings like call_blender_tool or run_blender_scene_stage. It stops short of naming its natural counterpart, search_3d_guidance, so sibling differentiation is only implicit.

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?

Usage is only implied: 'one approved Markdown reference' suggests retrieval of a specific already-known document, as opposed to searching. It never says when to prefer this over search_3d_guidance, nor what to do when the filename is unknown, so the agent must infer the search-then-read workflow.

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

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

No annotations are supplied, so the description carries the full burden, yet it never says whether this is a pure read, whether it mutates session state, whether it requires an active Blender connection, or roughly how much text it returns for 'compact'. The word 'compact' is the sole nod to output size, and 'public' is unexplained.

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?

A single front-loaded sentence with no padding or redundancy. It is efficient, though its brevity borders on under-specification rather than tightness.

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 zero-argument context loader the description should say what the agent receives and how it relates to the bootstrap sibling, especially since there is no output schema. It is minimally viable but leaves the agent guessing about the return payload and the sequencing.

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 input schema has zero parameters at 100% coverage, so there is nothing for the description to disambiguate. Baseline 4 applies for a no-parameter tool.

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 verb 'Load' and the object 'operating rules' give a rough sense of the operation, but 'compact ViperMesh operating rules' and 'persistent Blender MCP sessions' are product jargon that an agent cannot resolve from the text alone. It does not distinguish this from the sibling bootstrap_vipermesh_session, which plausibly loads overlapping session material.

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, when-not-to-use, or ordering guidance, and with siblings like bootstrap_vipermesh_session, check_blender_connection and list_blender_tools in the same family, the agent has no basis to pick this one first. 'Persistent Blender MCP sessions' is the only contextual hint and it is not framed as a condition.

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

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

With no annotations, the description carries the full behavioral burden and discloses almost nothing: it does not say the call is read-only, whether 'trusted local portable gateway' implies an auth/connection prerequisite, or whether results are cached or paginated. The single useful signal is that execute_code is exposed for fallback measurement.

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 compact sentence with no filler, and the core purpose is front-loaded. It is short to the point of under-specification rather than wordiness.

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 discovery tool with no output schema, no annotations, and two undocumented parameters, the description should at minimum explain what the listing returns (names only? schemas?) and how query/category narrow it. Neither is covered, leaving an agent unable to predict the response shape.

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 0% and the description says nothing about the two optional parameters, query and category, such as whether they filter by name, substring, or exact category value. The agent must guess the filtering semantics entirely from bare property names.

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?

States a specific verb and resource ('List Blender commands available through the trusted local portable gateway') and even names one returned item, execute_code. It does not distinguish itself from close siblings like call_blender_tool or check_blender_connection, so it falls short of a 5.

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 statement of when to call this versus call_blender_tool, call_blender_tool_batch, or check_blender_connection. The only hint is the parenthetical 'for fallback measurement' attached to execute_code, which does not tell an agent when to prefer this listing tool.

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

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

With no annotations, the description carries the full behavioral burden. It discloses one useful trait, that the session is persistent across calls, but says nothing about whether stages mutate prior scene state, what happens on a partial failure, whether a bootstrapped session is required first, or what the call returns.

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, front-loaded with the core action, and no filler. The second sentence carries real routing information but is vague about what the 'decision points' entail, so it spends words without fully earning them.

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 14-parameter mutation tool with no annotations and no output schema, the definition is materially under-specified. An agent cannot tell which of the many optional parameters each stage consumes, nor what a successful or failed stage looks like.

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 0% across 14 parameters, so the description must compensate and largely does not. Only the stage enum values are echoed; preset, samples, commands, blendPath, renderPath, previewPath, resolution, targetNames, spatialRelations, groundingTolerance, and preservePresentation are all left unexplained by both schema and description.

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 and resource: running one scene-workflow stage over a persistent Blender session, with build/inspect_preview/finalize named as the stages. It also distinguishes itself from the sibling standalone tools, though the word 'stage' alone would be opaque without the enum in the schema.

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?

It gives a clear workflow directive to treat build, inspect_preview, and finalize as separate decision points, and notes that standalone tools remain for repairs and unusual work. However, it never explains what each stage actually does or when a caller should pick inspect_preview over finalize, so stage selection is left to inference.

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

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It does not explain what "checked-in" means operationally, whether the semantic store requires configuration or authentication, what happens when the store is unavailable, or what the result format and pagination behavior are.

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 compact sentence with the core purpose front-loaded and no wasted wording. Its brevity is efficient, though it leaves important semantics unexplained rather than being structurally confusing.

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 search tool with no annotations, no output schema, and zero schema description coverage, the description is too thin to be complete. It omits result behavior, source selection details, and parameter meanings that an agent would need 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 0% across four parameters, so the description should compensate but mostly does not. It loosely hints at the semantic source option, but never explains query semantics, the meaning of the source enum values, the limit, or minSimilarity.

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 ("Search") and resource ("checked-in ViperMesh 3D tool skills" plus an optional semantic guidance store), so the agent can understand what the tool retrieves. It does not explicitly distinguish itself from the sibling get_3d_guidance_document, but the search-oriented framing is reasonably clear.

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 phrase "optionally the configured semantic guidance store" hints that the tool can search two sources, but it gives no explicit guidance on when to use this tool versus get_3d_guidance_document or list_blender_tools. There are no exclusions or conditions for choosing between local and semantic search.

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