domotz_alerts

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

Discloses workflow dependencies (list_profiles first), scope of get_device_bindings (all devices), and deprecation status. No annotations exist, so description carries full burden; it covers core behaviors but could mention mutation effects or idempotency.

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?

Well-structured with clear sections (action reference, gotchas, examples). Every sentence adds value; no redundancy. Front-loaded with purpose and action overview.

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?

Covers all actions, parameters, gotchas, and examples. Lacks description of return values (no output schema), but for a management tool, examples provide sufficient guidance. Could benefit from stating what each action returns.

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 has 100% coverage with parameter descriptions. The description adds critical context: which parameters are required for each action, the binding workflow, and the deprecation note, significantly aiding accurate invocation.

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 purpose: 'Manage alert profiles and their bindings to collectors and devices.' It then enumerates specific actions, which distinguishes it 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?

Provides explicit action reference with required parameters, gotchas (e.g., binding workflow, get_device_bindings behavior), and examples for common use cases. It also notes deprecation of list_profiles_deprecated, guiding the agent to prefer list_profiles.

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