cross_scene_set_property

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

No annotations provided, so description carries full disclosure burden. Fails to explain: (1) that additionalProperties allows arbitrary property key-values, (2) what timeoutMs measures (operation timeout? connection timeout?), (3) what autoConnect connects to, or (4) side effects on scene states. 'Compatibility tool' suggests legacy behavior but doesn't explain constraints.

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?

Extremely brief (6 words). The core action is front-loaded. However, given the tool's complexity (cross-scene mutations, timeout behavior, arbitrary property support), this is under-specification masquerading as conciseness rather than appropriate brevity.

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?

Severely incomplete for a mutation tool with no annotations. No output schema means description should explain return behavior or success/failure modes. Doesn't address: thread safety, scene loading requirements, transaction scope (all-or-nothing vs partial), or relationship to sibling batch_set_property. The additionalProperties capability alone warrants significant documentation.

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 has 0% description coverage, yet the description adds no parameter documentation. Critical omissions: timeoutMs semantics, autoConnect purpose, and crucially, that additionalProperties=true means users can pass arbitrary property names/values to be set. The description ignores the schema's extensibility entirely.

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 the basic action (Set) and scope (property across scenes), distinguishing it from single-node property setters like set_node_properties. However, 'across scenes' is ambiguous—does it mean multiple scenes simultaneously or persistence across scene transitions? The '(Compatibility tool)' parenthetical adds context but remains vague.

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?

Contains no explicit when-to-use guidance or alternatives. The '(Compatibility tool)' notation hints this may not be the preferred method, but fails to specify what the modern alternative is or when this specific tool is actually required. No mention of prerequisites or exclusions.

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