bosch_camera_lan_ping

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

No annotations are provided, so the description bears full responsibility. It discloses the protocol (TCP port 443), timeout (1.5 s), and return values (reachable, ip, latency_ms). This is sufficient transparency for a simple network probe. A minor gap: it doesn't explain behavior on timeout or invalid IP, but the return schema indicates those cases would likely return reachable=false.

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 concise: three sentences covering functionality, parameter usage, and return format. No redundant information. Front-loaded with the core probe action, then rationale, then output shape.

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 simplicity and the presence of an output schema (implied by context), the description fully covers the tool's purpose, parameters, and return value. Sibling tools are numerous but none overlap in functionality, so no further differentiation needed.

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 0%, so description must add meaning. It explains that 'camera' is resolved from bosch_config.json, while 'lan_ip' is a raw IP. It also implies mutual exclusivity by saying 'Pass either... or...'. This adds essential semantic value beyond the schema's basic type declarations.

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 probes camera LAN reachability on TCP port 443 with a 1.5s timeout. This is distinct from all sibling tools, which are about camera features like audio, motion, or streaming. The verb 'probe' and resource 'camera reachability' are specific.

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 explicitly advises when to use this tool: diagnosing cloud-down situations. It explains the consequence: if reachable, local writes (privacy/light) will work without waiting for Bosch infrastructure. This provides clear context and guidance, differentiating it from other tools.

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