object.set_visibility

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

Annotations indicate readOnlyHint=false, idempotentHint=false, and destructiveHint=false, but the description does not clarify the actual mutation semantics, side effects, or what happens to existing visibility states. The added 'Risk: standard; maturity: L3' text is generic metadata rather than behavioral transparency. There is no contradiction with annotations, but also no added behavioral context.

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 brief, but brevity here is under-specification, not conciseness. The first sentence restates the tool name, and the remaining risk/maturity/requirements text adds little actionable information. Every sentence should earn its place, and these mostly do not.

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?

With 8 parameters, low schema coverage, and a complex domain, the description is far from complete. It omits the tool's purpose, parameter semantics, effect on scene objects, and relationship to sibling tools. Even though an output schema exists, the agent has no basis to understand what the tool actually does or how to invoke it 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 only 38%, and the main functional parameters (name, render, objectId, viewport) have no schema descriptions. The tool description does not compensate by explaining any of these parameters or their relationships. An agent cannot determine what objectId or name mean, or how render/viewport flags behave, from the provided text.

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 only restates the command name and metadata: 'PartMe Blender Harness command `object.set_visibility`.' It does not say that the tool sets an object's viewport/render visibility, nor does it distinguish this from sibling tools like blender_object_set_display or blender_collection_set_visibility. This is essentially a tautology of the title.

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 about when to use this tool versus alternatives. The description only mentions generic 'requirements' that apply, not any scenario, prerequisite, or exclusion. An agent receives no help choosing between object.set_visibility and the many related visibility/display tools.

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