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

The annotations only declare readOnlyHint=false, destructiveHint=false, idempotentHint=false and openWorldHint=true; the description goes well beyond that by disclosing that the token is shown once, how it is transmitted (x-odile-run with the app key), the Idempotency-Key requirement for writes, and the recovery endpoint. It does not contradict the write/non-destructive annotation profile.

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?

Roughly 90 words, front-loaded with the core effect, and no sentence is pure filler. However, it reads as one dense paragraph that braids token issuance, idempotency rules and an edge-case recovery endpoint together, which slightly obscures what the primary call does.

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 an 8-parameter creation tool with nested action objects and no output schema, the description supplies the missing return detail (a one-time run token, shown once) and the auth/idempotency contract. Remaining gaps (e.g. what else the response contains, interplay of max_calls vs per-action max) are minor since the schema covers those fields.

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 100%, so the baseline is 3, but the description adds a concrete rule example ('PATCH /customers/{customer}/tickets/:id' with scope {"customer":"A"}) that clarifies how the actions, scope, check and approval fields interrelate in a way the schema alone does not.

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 first sentence states a specific effect: give one agent session narrow, expiring permission, and the token issuance is spelled out later ('Returns a run token (shown once)'). This distinguishes it from siblings like gate_create_project or gate_set_app_runs, though the framing as 'Gate Actions' is jargon-heavy rather than plainly saying 'create a run'.

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 description explains operational conditions (writes need an Idempotency-Key, give a write a check so the agent can recover) but never says when to choose this tool over its siblings such as gate_set_app_runs, nor states prerequisites or exclusions. Usage must be inferred from the mechanics.

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