wordpress_wp_transient_delete_all

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

With no annotations provided, the description must carry the full burden of behavioral disclosure. It adequately specifies scope ('all expired') and effect ('cleaning up temporary cached data'), but fails to mention safety aspects like irreversibility, error conditions, or required authorization levels for this destructive operation.

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 two-sentence structure is efficient and front-loaded with the action, but the '[UNIFIED]' prefix adds metadata noise without providing value to the agent. Otherwise, every sentence earns its place by describing action and benefit.

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 simple maintenance tool with one parameter and no output schema, the description adequately covers the operation's intent but remains incomplete due to the critical omission of parameter semantics and lack of behavioral safety context that would normally be provided by annotations.

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?

The input schema has 0% description coverage for the required 'site' parameter, and the description completely fails to compensate by explaining what constitutes a valid site identifier (e.g., site ID, domain name, or slug). This leaves the critical parameter undocumented.

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 provides a specific verb ('Delete') and resource ('all expired transients from the database'), clearly stating the tool's function. The second sentence adds value by explaining the benefit ('Improves database performance'). It loses a point for not explicitly differentiating from the sibling tool `wordpress_wp_transient_list`, though the verb distinction is implicit.

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?

While it implies a use case via 'Improves database performance,' it lacks explicit guidance on when to use this versus alternatives like `wordpress_wp_cache_flush` or `wordpress_wp_transient_list`. It also omits prerequisites such as required permissions or safety considerations for database cleanup.

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