set_scene_item_enabled

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

With no annotations, the description carries the burden of behavioral disclosure. It clarifies the enabled parameter's meaning, which is helpful, but it does not disclose any side effects, return values, or required permissions. For a simple setter, this is adequate but not rich.

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 extremely concise, with a clear one-line purpose followed by a compact Args list. Every sentence serves a purpose, and there is no wasted text.

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 low complexity (3 required parameters, no output schema, no annotations), the description covers all essential information: what the tool does, what parameters to pass, and what the boolean means. Nothing critical is missing.

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 schema properties have no descriptions (0% coverage), and the description fully compensates by explaining each parameter: scene_name, scene_item_id, and enabled with explicit boolean semantics. This adds significant value beyond the structured 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 begins with 'Show or hide a scene item,' which is a specific verb+resource pair that clearly differentiates this tool from siblings like set_scene_item_locked or get_scene_item_enabled. The purpose is unambiguous.

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 description clearly implies use for setting visibility of a scene item, and its parameter explanations support correct usage. However, it does not explicitly mention alternatives or exclusions, though the context makes it obvious.

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