domotz_configuration

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

With no annotations, the description fully covers behavioral traits: it lists all actions, required parameters, and body requirements. It discloses the backup workflow sequence and notes which actions need a body. However, it does not mention idempotency, rate limits, or error handling.

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-structured with sections: summary, action reference, gotchas, and examples. Every sentence adds value, and critical information is front-loaded. No wasted text.

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 complexity (multiple actions, 5 params, no output schema), the description covers actions, parameters, workflow, and examples. It lacks explicit return value descriptions and error conditions, but the examples and action list are sufficient for basic usage.

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?

Input schema coverage is 100%, but the description adds meaning by specifying which actions require the 'body' parameter and that 'configuration_timestamp' is used for 'get_config'. Examples further illustrate parameter usage, going beyond pure schema documentation.

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 'Manage device configuration backups, credentials, and SNMP authentication,' which specifies the scope. The action reference lists eight distinct operations, differentiating this tool from siblings like domotz_agents or domotz_monitoring.

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 provides a 'GOTCHAS' section explaining the backup workflow order and notes that agent_id and device_id are required for all actions. However, it does not explicitly compare to siblings or state when not to use this tool, so implicit usage context is strong but lacks exclusions.

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