domotz_network

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

No annotations are provided, so the description bears full burden. It does not disclose whether actions are destructive, reversible, or require special permissions. While it lists actions like delete/set, it offers no warnings about their effects.

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 well-organized into an introductory line, an action reference, and examples. It efficiently conveys necessary information without redundancy, though the action list is somewhat lengthy.

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 has no output schema, so return values are undefined. The description covers operations and parameters adequately for a configuration tool, but lacks details on pagination, error handling, or rate limits.

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 100% and describes basic parameter types. The description adds value by mapping each action to required parameters (e.g., body for set/create, device_id for excluded) and providing concrete usage examples.

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 it manages network scan policies, interfaces, routed networks, and excluded devices. It enumerates 14 specific actions and provides examples, making the tool's purpose distinct from sibling tools like domotz_agents or domotz_devices.

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?

It explicitly requires agent_id for all actions and links actions to required parameters (e.g., device_id for excluded devices). Examples demonstrate correct usage. However, it does not explicitly state when to avoid this tool in favor of siblings.

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