Set Property

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

The description adds behavioral context beyond annotations: it notes the Edit Mode limitation, explains dry_run as a safe preview, and details how ref_component_type resolves plain scene paths. Annotations already indicate idempotency and non-read-only, so the description supplements without contradicting them.

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 dense but purposeful. Every sentence covers a distinct concept (mode, find_type, rename alternative, value formats, dry_run, ref_component_type) with no filler. A minor typo ('BoxClider') does not affect understandability.

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 tool's complexity (7 params, no output schema), the description covers the key operational modes, bulk behavior, reference format details, and safety preview. Combined with the strong schema descriptions, it gives the agent enough to select and invoke 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 high (86%), and the description further clarifies find_type for bulk operations, dry_run's preview effect, ref_component_type (which has no schema description), and the complete ObjectReference value format. This goes beyond the structured fields.

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 a component property, with a specific verb and resource. It distinguishes itself from siblings by explicitly mentioning Edit Mode/SerializedObject and contrasting with Play Mode tools like invoke_method/execute_code, plus rename_object() for renames.

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 explicit usage context: 'Edit Mode, SerializedObject' and directly names alternative tools for Play Mode ('use invoke_method or execute_code') and for renames ('use rename_object()'). This makes the when-to-use boundary crisp.

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