Update Trigger

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

With no annotations, the description carries the behavioral burden. It clearly discloses the replace-not-patch semantics and the destructive effect of omitting fields. This is critical behavioral information beyond what the schema states, though it does not cover authentication, rate limits, or response behavior.

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?

Two tight, information-dense sentences. The critical replacement semantics are stated up front, and there is no filler or redundant restating of the tool name.

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 full parameter schema coverage, an output schema, and a description that explains the core replacement behavior, the agent has enough context to call the tool correctly. The fingerprint concurrency mechanism is already documented in the schema, so its absence from the description is not a gap.

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 all parameters. The description adds meaningful context for the 'trigger' parameter by emphasizing it must be the complete resource and replaces the stored one, but it does not elaborate on the ID parameters or fingerprint beyond what the schema provides.

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?

States a specific verb ('Update'), resource ('trigger'), and scope ('in a workspace'). Clearly distinguishes from sibling trigger tools like create_trigger, get_trigger, delete_trigger, and revert_trigger.

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 usage guidance: read the trigger with get_trigger first, send the whole resource back with edits, and know that omitted fields are cleared. This effectively tells the agent how to invoke the tool correctly, though it does not explicitly contrast with create_trigger or revert_trigger.

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