set_trigger_pattern

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

Without annotations, the description carries the full burden. It adds useful behavioral detail (pattern syntax, auto-expansion, level requiring level_source), but does not state that this is a write operation, whether it alters existing trigger settings, or what permissions are needed.

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 compact and front-loaded with the tool's purpose, then breaks down parameters. The SCPI command hint at the end is useful and terse, though the opening line is abrupt.

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?

An output schema exists, so return values need not be explained. However, missing usage context and incomplete parameter coverage (source, extra) leave the definition only marginally complete for an agent without domain knowledge.

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 0%, so the description must explain all parameters. It clarifies pattern, level, and level_source, but completely omits 'source' and 'extra', leaving two of five parameters undocumented.

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 and tool name together make clear this configures a pattern trigger, a specific trigger type distinct from edge, pulse, etc. The first line 'Pattern trigger.' is terse but sufficiently identifying combined with the name.

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?

No guidance on when to use this pattern trigger versus other trigger types like edge, pulse width, or window. No prerequisites or context about trigger mode are provided.

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