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

Annotations already declare readOnlyHint and idempotentHint, so the agent knows this is a pure, repeatable generation with no side effects. The description adds that defaults target a 'pnpm standalone image', which is useful context, but it doesn't disclose what happens if the flags conflict (e.g. migrate without prisma) or how the multiple artifacts are returned.

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 tight sentences, artifact list front-loaded, no filler. Every clause carries information.

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?

Output format is covered by the output schema and the safety profile by annotations, so those needn't be restated. However, for a tool exposing 13 undocumented configuration parameters, the description is thin and leaves most option semantics to inference.

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?

With 0% schema coverage across 13 parameters, the description carries the full burden but only hints at two defaults (packageManager=pnpm, standalone=true). It says nothing about base, node, port, turbo, prisma, migrate, healthPath, publicEnvs, cacheMounts, healthcheck, or telemetryDisabled.

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 (Generate) and enumerates the exact artifacts produced: Dockerfile, dockerignore, compose file, and next.config snippet. No sibling tool overlaps this domain, so the tool is easily identifiable.

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 only scoping is 'for a Next.js app'. There is no statement of when to reach for this versus hand-writing a Dockerfile, no mention of prerequisites (existing package.json, pnpm lockfile), and no when-not guidance.

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