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

Annotations only declare the generic non-read-only, non-idempotent, non-destructive profile, while the description adds substantial specifics: the rollout replaces pods with the new environment using the recorded identity, it applies the just-saved config, it stays isolated in a TTL-reaped namespace, and per-launch overrides merge over saved defaults. These are exactly the behavioral traits annotations cannot convey.

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 action and scope are front-loaded in the first sentence, with rationale and override behavior following. It is a dense paragraph with several clauses, but each sentence carries distinct information about identity reuse, safety, and overrides rather than padding.

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 six-parameter mutation tool with no output schema but present annotations, the description covers the redeploy mechanics, override semantics, demo identification, and ask-mode safety. Only an explicit statement of expected outcomes or an exclusion against sibling demo-creation tools 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 description coverage is 100%, so the baseline is 3, but the description adds real meaning beyond the schema by explaining that env/database are per-launch overrides layered on top of saved defaults (defaults that env values win over by name). It also explains demo identification via workspace_id or namespace, going beyond the bare schema fields.

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 gives a specific verb and resource ('Redeploy an existing Application demo (PR or branch)') and immediately scopes it against alternatives by noting the demo identity, branch/PR, and image tag are reused rather than chosen fresh. An agent can distinguish it from deploy_pr_demo or update_application_demo_config without opening any 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 states the concrete trigger ('This is how a crashed demo is relaunched after update_application_demo_config') and the safety condition ('Safe in ask mode'). It does not, however, state an exclusion against the sibling deploy_pr_demo for brand-new launches, so the guidance is clear but not fully routing.

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