shelly_discover

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so 'Safe, read-only' is largely redundant. The genuinely additive parts are the disclosure that mDNS discovery is time-bounded and that the result is a 'lightweight identity' set requiring a follow-up probe, which tells the agent not to expect full device state here.

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?

Three short segments, front-loaded with the core action, then parameter notes, then safety/return caveat. No padding or filler sentences; the markdown-style backticks are slightly noisy but harmless.

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?

With an output schema present, return values need not be spelled out, and the description still adds the useful 'probe for detail' caveat. Covers purpose, both parameters, safety, and LAN/cloud behavior; the only real gap is interaction with the shelly_list_devices sibling.

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 0%, so the description carries the full burden and does explain both parameters: timeout_s as the mDNS browse window and use_cloud=false as the LAN-only switch. It omits the schema defaults (5 and true), but the meaning and effect of each parameter are clear.

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 a specific verb and resource with its discovery mechanism: 'Discover Shelly devices on the LAN via mDNS, merged with the cloud account list.' It is concrete about scope (LAN + cloud), though it does not distinguish itself from the sibling shelly_list_devices, which an agent could reasonably confuse it with.

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?

Gives a conditional usage hint for a parameter ('Set use_cloud=false to skip the cloud list (LAN-only)') and implicitly routes detail-seeking callers elsewhere via 'probe for detail'. However, it never explicitly says when to prefer this over shelly_list_devices or which sibling to call for the referenced detail.

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