Deploy WordPress theme

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

Annotations already signal readOnlyHint=false and destructiveHint=true. The description adds useful behavior beyond that: it uploads all theme files, triggers deployment, supports optional activation, and manages credentials internally. It does not describe exact destructive effects, but the annotation covers the destructive nature and the description adds meaningful context.

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 three focused sentences with no filler. The main action is front-loaded, and the critical instruction about not calling a separate upload-url endpoint is included without bloating the text.

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 operation with fully documented parameters and destructive/read-only annotations, the description covers the workflow end-to-end: source directory, deployment trigger, optional activation, and internal credential handling. It does not specify return values or async behavior, but that is not a critical gap for this tool.

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 schema already documents all four parameters. The description adds only light mapping by mentioning 'from a directory' for themePath and 'optionally be activated' for activate, but it does not need to provide deeper parameter semantics.

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 opens with a specific verb and resource: 'Deploy a WordPress theme from a directory to a hosting server.' It further distinguishes itself from upload-only or install workflows by stating it uploads all theme files, triggers deployment, optionally activates the theme, and works end-to-end without a separate upload-url call.

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 gives clear operational guidance: upload credentials are generated internally, and the agent should not call a separate upload-url endpoint or upload files manually. It does not explicitly name sibling alternatives such as install or activate theme tools, but the local-directory deploy use case is clear enough.

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