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

Annotations already flag destructiveHint=true and non-idempotent, but the description adds real behavior: the app is restarted if it was running, and passing repo/branch repoints the deployment configuration rather than just fetching code. Remaining gaps are operational details like downtime or behavior on pull failure, which keeps this below a 5. No contradiction with the 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?

Two sentences with no filler, and the core action plus restart caveat is front-loaded. The second sentence is dense and slightly awkward ('Pass branch, and repo if it changed, to FIX'), which costs a bit of readability.

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 destructive, non-idempotent mutation tool with no output schema, the description covers side effects, recovery semantics, and what not to do instead. Only minor operational context (failure behavior, whether the restart is guaranteed) is missing.

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 67% and the schema already documents repo and branch adequately ('Omit to keep the current one'). The description adds the consequence of passing them (repointing the deployment for recovery), but says nothing about the required 'id' parameter or expected format, so it only modestly exceeds the schema.

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 and resource ('Pull the latest code from the linked GitHub repo') plus the key side effect (restart if running). It also distinguishes the recovery path from deleting/recreating the deployment, so an agent can tell it apart from deployments_create/delete workflows.

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?

Gives explicit when-to-use guidance for the optional parameters ('to FIX a wrong branch after a failed clone') and explicitly rules out the destructive alternative ('never deleting and recreating'). It stops short of positioning itself against nearer siblings such as deployments_apply or deployments_update, so the choice between those remains inferred.

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