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

Goes well beyond the destructiveHint annotation: discloses the delete_themes capability requirement, DISALLOW_FILE_MODS refusal, permanence with no undo point, and the exact return fields (deleted, stylesheet). Also notes the request is forwarded to a single site via AlphaBridge Connect, which is non-obvious behavioral 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?

Dense and front-loaded: the delete action comes first, then refusal rules, then side effects and return values. No sentence is filler despite covering several distinct facts.

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?

No output schema exists, but the description names the returned fields and covers permissions, refusals, and irreversibility. The only thin spot is that permanent deletion scope (database rows vs. files) is implied by "folder and files" rather than spelled out.

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 the schema already defines stylesheet as the exact installed directory name with an example, so the description adds no parameter-level detail beyond it. Baseline 3 is appropriate when the schema does the heavy lifting.

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 and resource ("Delete an installed theme's folder and files") and makes the scope concrete, distinguishing it from wp_update_theme and wp_activate_theme by naming both siblings.

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?

Explicitly states what is refused (active theme, parent theme) and routes to the correct alternatives: wp_activate_theme for switching, wp_update_theme for a newer version without deletion.

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