zda_reorder_triggers

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

No annotations are provided, so the description carries full burden. It discloses the guarded behavior (preview-then-apply) and warns about routing bugs. However, it does not mention permissions required or the exact effect of reordering (though it implies non-destructive change). Still, the behavioral context is well covered.

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?

Three sentences of increasing specificity: purpose, guarded behavior, input requirement. No redundant or unnecessary text. Perfectly sized and front-loaded.

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 no output schema, the description could specify the return format (e.g., preview returns current order). However, the tool is simple with two parameters, and the description covers usage, input, and behavioral context adequately. Slightly lacking on output specifics.

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 50%, but the description adds value for the 'require_confirm' parameter by explaining its role in preview vs apply. The 'trigger_ids' parameter is described as the complete ordered list, which matches the schema. Overall, the description enhances parameter understanding.

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: 'Reorder triggers.' It explains the importance: trigger order determines evaluation precedence and is a common source of silent routing bugs. This distinguishes it from sibling tools like zda_update_trigger or zda_list_triggers.

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?

Explicit usage guidelines are provided: 'GUARDED: call without require_confirm to preview the current order; re-call with require_confirm: true to apply.' This tells the agent when to use, how to preview, and how to apply, with clear instructions to provide the complete ordered list.

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