Prepare Compose project adoption

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

Annotations declare non-read-only, non-destructive, idempotent, closed-world. The description adds rich context beyond that: it verifies container identity, image identity, restart policy, Compose safety, and volume ownership; it returns only a scrubbed Compose file, variable names, and bounded counts while never returning variable values, source paths, commands, or unrestricted labels; it does not stop or replace containers; and it requires applications:manage.

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 front-loaded with purpose and packs verification, return, and permission details efficiently. It is slightly dense but every sentence earns its place; no wasted preamble.

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 security-sensitive adoption-prep tool with no output schema, the description covers prerequisites, verification scope, return scrubbing, and safety profile. Together with annotations and the fully described schema, an agent has enough to call it correctly.

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 100% and all three parameters already have detailed descriptions. The description adds only the qualifiers 'one exact unmanaged Compose project' and 'fresh discovery' which map to schema parameters but add no syntax or format detail. Baseline 3 applies.

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?

Names a specific compound action (prepare and poll), the resource (takeover candidate for one exact unmanaged Compose project), and the required source (a fresh discovery). This clearly distinguishes it from siblings like confirm_application_compose_adoption and get_application_compose_adoption.

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?

Provides clear context: it must be used on an exact unmanaged Compose project from a fresh discovery, and it signals a prerequisite via 'Requires applications:manage.' However, it does not explicitly name alternatives (e.g., confirm_application_compose_adoption) or state when not to use it.

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