Search event scripts

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint, so the safety profile is covered. However, the description itself adds no behavioral detail beyond a UI cross-reference; it does not mention case-insensitivity, pagination, or any side effects, relying entirely on schema and hints.

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: the core purpose appears in the first sentence. The second sentence is a terse cross-reference that is arguably cryptic, but it is not wasteful. Overall it is appropriately concise for a simple search tool.

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 read-only search tool, the schema and annotations already convey most of what an agent needs. The main missing piece is guidance on when to use this tool relative to similar siblings like search_devices_tool, so the description is adequate but not rich.

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%: query, limit, and offset each have descriptions. The tool description adds no parameter-specific meaning beyond restating that a string is searched, so it sits at the baseline for fully documented schemas.

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 specific action ('Search') on a specific resource ('string in scripts'), and the title clarifies that scripts are event scripts. It is plainly distinguishable from the sibling search_devices_tool, but it does not explicitly name that alternative or otherwise call out the distinction.

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?

There is no guidance on when to use this tool versus alternatives. The 'Cross-ref: domoticz://events' line points to a context, but it does not explain usage contexts, exclusions, or when another search tool such as search_devices_tool would be more appropriate.

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