connect_bulb

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It does not mention side effects, error handling, authentication requirements, timeouts, or whether establishing a connection is required before other operations. The only extra behavioral hint is the mock/real support, which is more about parameter semantics than behavior. This is a significant gap for a connection tool.

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 two sentences with zero fluff. The core purpose is front-loaded, and the second sentence adds relevant context about supported bulb types. Every word earns its place.

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?

The tool is simple (3 params, 1 required) and the schema is complete, so the description covers the basics. However, it does not mention that the connection is a prerequisite for the sibling bulb-control tools or that a disconnect_bulb exists, leaving the lifecycle unclear. Some context about the overall workflow 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?

Schema description coverage is 100% — all three parameters (ip, port, type) are fully documented with descriptions and defaults. The description adds no information beyond what the schema already provides; the mention of mock vs. real simply echoes the enum descriptions. Baseline 3 applies because the schema does the heavy lifting.

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 specific action ('Connect to a smart bulb at a given IP address') and the resource (smart bulb). It also mentions support for real Yeelight and mock bulbs, which distinguishes it from sibling tools that handle state, power, brightness, and color. This is a precise verb+resource statement with no ambiguity.

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 gives partial guidance by noting that mock bulbs are for testing, which helps with the type parameter, but it does not explicitly state when to use this tool versus its siblings (e.g., before get_bulb_state or set_bulb_*). The usage context is implied rather than clearly articulated.

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