set_object_visibility

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

No annotations provided. Description mentions both viewport and render visibility with defaults, and returns a confirmation dict. However, it omits behavioral details like error handling, reversibility, or effects on other tools (e.g., object still selectable).

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 with structured Args and Returns sections. No fluff, every sentence earns its place. Front-loaded with the main action.

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?

Tool is simple with 4 parameters, all documented. Has output schema (implied by Returns). No example provided, but completeness is adequate for the complexity. Minor gap: no mention of object type requirements.

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 0%. Description explains each parameter (name, visible, viewport, render) with defaults and purpose, adding meaning beyond schema names. Could include examples or constraints but sufficient for basic understanding.

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 tool sets object visibility in viewport and/or render, using a specific verb 'Set' and resource 'object visibility'. It distinguishes from sibling tools like 'set_collection_visibility' and 'set_object_property' ones.

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?

No guidance on when to use this tool versus alternatives (e.g., set_collection_visibility, select+hide). Lacks when-not-to-use and context about prerequisites like object existence.

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