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

Annotations already declare destructiveHint=true and openWorldHint=true, so the safety profile is covered. The description adds substantial context beyond that: which resources are preserved (managed databases, volumes, secrets, env vars) and how env vars can be overridden. It does not cover auth requirements or rate limits, but the preservation/overwrite semantics are valuable.

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 dense sentences, front-loaded with the default in-place behavior before the conditional new-deployment case. Every clause contributes, though the parenthetical override note is slightly compressed given the number of fields it references.

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 mutation tool with no output schema, the description adequately explains the in-place-vs-new decision and preserved state. However, with a nested 11-property overrides object that is almost entirely undocumented in both schema and description, an agent lacks guidance on most override fields, leaving a meaningful gap.

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 0%, so the description must carry the burden. It adds meaning for overrides.envVars and names name/provider/code/dockerfile as new-deployment triggers, but leaves the other override fields (region, framework, displayName, healthCheckUrl, autoDestroyHours, etc.) and the required deploymentId entirely unexplained. It partially compensates but leaves clear gaps.

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 names a specific verb and resource ('Rebuild a deployment IN PLACE') and precisely defines the default scope: same deployment id and URL. It further distinguishes its behavior from nexusai_deploy_create by stating that a NEW deployment only happens under specific override conditions, so an agent can tell the two apart without opening either schema.

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?

It gives clear context for when the in-place behavior applies versus when a new deployment is spun up (overrides set name/provider/code/dockerfile, or non-repo sources). It does not explicitly name sibling alternatives like deploy_rollback or deploy_create, so it stops short of full 'when-not' guidance, but the conditional logic is well conveyed.

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