Deploy Agency PHP Application

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

With no annotations, the description carries the burden. It discloses extraction, as-is serving, no build step, and synchronous operation, but does not mention potentially destructive aspects like overwriting existing content or required file structure.

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?

Three sentences with no fluff. First sentence gives the core purpose, second clarifies behavior, third clarifies operation mode. Each sentence earns its place.

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 deploy tool with no output schema, the description covers the essential behavior. It is missing minor context like what happens to existing site content, but overall is sufficient for an agent to invoke 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%, so descriptions for both parameters already exist. The tool description adds no parameter-specific meaning beyond 'archive' and 'PHP application', so baseline of 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?

The description clearly states the action ('Deploy'), the resource ('PHP application to an Agency Plan website'), and the source ('from an archive'). It also differentiates from sibling deploy tools by noting 'no build step'.

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 context is clear: use for PHP apps on Agency Plan sites from an archive. However, it does not explicitly mention when not to use it or name alternative tools for other deployment types, so it lacks explicit exclusions.

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