Add Domoticz log message

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

Annotations already declare readOnlyHint=false, idempotentHint=false, destructiveHint=false, so the agent knows this is a non-read, non-idempotent operation. The description adds the level enum semantics (1=Normal, 2=Status, 4=Error) and a cross-reference to `domoticz://logs`, which is useful context. However, it doesn't disclose what happens on success/failure, whether the message is truncated, or any side effects beyond writing to the log.

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 very short and front-loaded: 'Log message' immediately states the action. The level mapping is compact and useful. The cross-reference is a single extra detail. No wasted words, though it could arguably be even more informative without becoming bloated.

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?

For a simple 2-parameter tool with 100% schema coverage and an output schema, the description is mostly adequate. The main gap is that it doesn't explain the behavior of the log (e.g., whether messages are visible immediately, any rate limits, or what the output schema contains). The cross-reference to `domoticz://logs` hints at where to view results, which helps, but the description could be more complete about the operation's effect.

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 description coverage is 100%, so the schema already documents both parameters. The description adds the level mapping (1=Normal, 2=Status, 4=Error) which is also in the schema's enum descriptions, so it's redundant. The cross-reference to `domoticz://logs` adds a small amount of context but doesn't meaningfully enhance parameter understanding beyond the schema.

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 a clear verb+resource: 'Log message' with level semantics. It distinguishes itself from siblings by being the only logging tool among the listed siblings, though it doesn't explicitly name an alternative. The title 'Add Domoticz log message' reinforces the 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?

The description implies usage: it's for adding a log message to Domoticz, with level values explained. It doesn't explicitly state when to use this vs alternatives, but the sibling list contains no other logging tool, so the context is clear enough. No exclusions or alternative routing are provided.

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