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

The description adds a valuable behavioral detail beyond the annotations: config_patch merges key-wise and explicit null deletes a key. While this is also in the schema's description, it is a critical semantic trait that prevents an agent from treating config_patch as a full replacement. Since readOnlyHint=false and destructiveHint=false are already in the annotations, this extra merge context is the main enrichment.

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 a single, well-formed sentence that starts with the action and primary fields, then adds the essential config_patch semantics. There is no wasted phrasing or repeated metadata. The parenthetical is tightly integrated and necessary for correct invocation.

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?

With full schema documentation and read/write/destructive hints provided in annotations, the description is mostly sufficient, but lacks discussion of what happens when the deployment_id doesn't exist, whether the operation is idempotent, or what kind of response is returned (no output schema is present). These modest gaps keep it from being fully complete for an agent invoking the tool cold.

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?

The input schema already provides 100% coverage of all four parameters, including descriptions like 'New name.' and 'Partial config to merge in (key-wise; null removes a key).' The description lists these fields and repeats the merge behavior, but it adds no meaning beyond what the schema already conveys. This is the baseline 3 for strong schema coverage.

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 states a clear verb: 'Patch a deployment's name/description/config.' It identifies the resource and the specific fields, which distinguishes it from sibling tools like create_deployment or activate_deployment. It doesn't explicitly name the alternatives, so I don't give a 5, but the primary purpose is unambiguous.

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 implies this is for modifying an existing deployment, but gives no explicit direction on when to use it versus create_deployment or update_agent. An agent must infer the intended context from the resource name and the word 'patch'. It is minimally adequate, but lacks any 'when-not-to-use' guidance.

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