sonoff_list_devices

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

No annotations are provided, so the description must disclose behavioral traits. It only states 'List all Sonoff/eWeLink devices', which implies a read-only operation but does not mention side effects, authentication, pagination, or return format. This is a minimal disclosure with potential gaps.

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 a single, front-loaded sentence with no fluff. It is concise and direct, though it lacks detail that would make it 'excellent'. The brevity is appropriate for a simple list operation, but it borders on under-specification.

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 no annotations or output schema, the description should explain what the tool returns and how the required parameter relates to the action. It does neither. The odd requirement of a device_id to list 'all' devices is also unaddressed, making the context incomplete.

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 description covers the one parameter (device_id) with 'Sonoff/eWeLink cloud account device ID', so schema coverage is 100%. The tool description adds no additional meaning beyond what the schema already provides, which is acceptable given the high coverage.

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's verb and resource: 'List all Sonoff/eWeLink devices'. It is specific and distinguishes from non-Sonoff tools, though it does not differentiate from other brand-specific list tools (e.g., tuya_list_devices) beyond the brand name.

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?

No guidance is provided on when to use this tool versus alternatives. The description only gives the action and resource, with no mention of suitable contexts, prerequisites, or exclusions, leaving the agent to infer usage from the sibling tool names.

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