post_lan_wol_interface

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

Lists error codes but fails to clarify success behavior, permissions, or side effects. The mention of optional password contradicts the schema, reducing trust.

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?

Two sentences with error codes, but lacks param documentation. Concise but incomplete and misleading.

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?

Fails to define the crucial 'interface' parameter or explain its format. No output schema or result description. Agent cannot reliably invoke the tool.

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 'interface' parameter has no description in schema (0% coverage) and description does not explain it. Instead describes non-existent parameters (host, password), providing no semantic value.

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 states it sends a WoL packet to a host with optional password, but the only required parameter is 'interface', not host or password. This mismatch between description and schema creates confusion about the tool's actual purpose.

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 on when to use this tool versus siblings (many other post_* tools) or alternatives. No prerequisites or context mentioned.

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