portainer_stack_deploy

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

No annotations are provided, so the description carries the full burden. It states the tool creates a stack but does not disclose side effects, authentication requirements, error handling, or whether the endpoint_id defaults. Minimal behavioral insight.

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 sentences plus parameter lines with no wasted words. The action is front-loaded, and every line adds value.

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?

The description covers core functionality and parameter explanations. Since an output schema exists, it need not detail return values. However, it omits context like default endpoint behavior beyond a brief note, and lacks error or validation details.

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 compensate. It provides docstring-style explanations for each parameter (name, compose_content, endpoint_id), adding meaning beyond the schema's titles and types. Notably, it clarifies that endpoint_id defaults if omitted.

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 clearly states 'Deploy a new stack from a docker-compose string', providing a specific verb and resource. It is distinct from sibling tools like portainer_stack_update (update) and portainer_stack_delete (delete), which are explicitly for different operations.

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 creation of a new stack, but does not explicitly state when to use this tool over alternatives like stack_update. It lacks when-not-to-use guidance or mentions of prerequisites.

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