Update Rules Priorities

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

Annotations already disclose readOnlyHint=false and idempotentHint=true, and the description adds little beyond noting it's a POST batch operation. It lacks details on failure semantics or auth, but the endpoint and 'single request' provide some context. No contradiction with annotations.

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 one sentence, front-loaded with the HTTP method and action, and contains zero filler. It efficiently conveys the purpose without redundancy.

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 one-parameter batch operation with a comprehensive schema and no output schema, the description is nearly complete. It could add a note about atomicity or partial failure behavior, but given the minimal complexity, it is adequate.

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% with meaningful descriptions for 'id' and 'priority' (including the higher-values-first behavior). The description's mention of 'execution priority' adds no new parameter information beyond what the schema already provides, so it defaults to baseline.

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 action ('Batch update') and target ('execution priority of multiple rules'), distinguishing it from siblings like gorgias_update_rule (single rule) and gorgias_list_rules (listing). It is specific and directly tied to the endpoint's 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 wording 'in a single request' conveys the batch use case, strongly implying this tool is for updating multiple rule priorities at once. It does not explicitly name alternatives or state when not to use it, but the context is clear enough to guide selection.

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