Fire a bridged light

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

Discloses the sunLight bug causing crashes, that the tool is one-way fire-only, and that MCP tracks sent value not actual state. Comprehensive given no annotations.

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?

Efficiently packed with all necessary details, no redundancy, each sentence adds value, well-structured with purpose, special cases, requirements, and limitations.

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?

Covers prerequisites, edge cases (sunLight bug), limitations (no getter), and source. With no output schema or annotations, this description is fully adequate for an agent to use the tool 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 coverage is 100%, but description adds crucial context: toggle and intensity are ignored for sunLight, and explains the fire-only nature of sunLight beyond enum values.

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?

Clearly states it drives ambient light intensity via bridge graph's TriggerNode, lists specific keys (bloom, vignette, ambientLight, sunLight), and distinguishes from sibling tools like vnyan_bridge_graph which installs the graph.

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?

Explicitly notes when not to use certain parameters (sunLight ignores intensity/toggle), requires prior install of vnyan_bridge_graph, and explains that no getter exists, so agent knows not to expect readback.

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