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

Beyond the annotations, the description discloses permission requirements (manage_options), return behavior including the false case when nothing is deleted, prefix filtering rules, and that the call is forwarded to one connected site. This adds substantial operational context for a destructive tool.

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 definition is front-loaded with the core operation and then adds only relevant constraints, return behavior, permissions, alternatives, and forwarding context. Each sentence contributes useful information without redundancy.

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 single-parameter tool with no output schema and annotations that already cover safety characteristics, the description is complete. It covers naming rules, permissions, return semantics, sibling alternatives, and connection behavior.

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 schema already documents the single name parameter at 100% coverage, so the baseline is 3. The description adds meaningful detail beyond the schema by naming the allowlist filter and stating that the plugin's own ab_mcp transient state is never allowed, though it does not enumerate all allowed prefixes.

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: "Delete one transient by name." It clearly scopes the operation to a single named transient, distinguishing it from sibling tools such as wp_set_transient and wp_cleanup_transients.

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?

It explicitly contrasts this tool with wp_set_transient (sets one) and wp_cleanup_transients (removes expired ones), which tells the agent when this tool is the appropriate choice. The prefix allowlist and prohibition on the plugin's own ab_mcp state further constrain correct usage.

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