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

Annotations already declare destructive/write behavior, but the description adds substantial context beyond them: whole-file backup before every edit, `php -l` syntax re-check with automatic revert, restore semantics, confirm=false preview vs confirm=true apply, and the narrow scope rules (theme folder only, specific extensions, no '..' escapes, never creates files).

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?

Purpose and scope are front-loaded, and the action-mode-safety ordering is logical. The prose is dense and lengthy, with some sentences carrying several ideas at once, but for a 9-param mutating tool most of the content 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?

Given a write tool with 9 params, zero schema descriptions, and an output schema already handling return values, the description covers scope, actions, edit modes, safety/revert behavior, and preview semantics. Nothing essential for correct invocation appears missing.

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 0%, so the description must carry the load, and it largely does: action values, path format with concrete examples, mode values, contains/find/replace semantics, and count's abort-if-exceeded behavior are all spelled out. Minor gap: site_url is never addressed, and defaults aren't noted.

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+resource ('Read and safely edit the ACTIVE THEME's own files') and immediately scopes it as a last-resort capability. It explicitly distinguishes itself from wordpress_option (plugin/theme settings) and wordpress_snippet (new PHP via WPCode), so an agent can route correctly without opening other schemas.

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 frames when to use it ('the last resort for things baked into a theme file that nothing else can reach') and why siblings can't cover that case. It then documents each action value (list/get/edit/restore) and, for edit, which mode to pick for which scenario (strip a gtag via remove_block, turn H4 into H2 via replace).

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