wordpress_flush_rewrite_rules

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

No annotations are provided, so the description carries full burden. It mentions the tool 'fixes permalink issues,' which hints at a corrective action, but fails to disclose critical behavioral traits such as whether this is a destructive operation, requires specific permissions, impacts site performance, or has side effects like regenerating URLs.

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 a single, efficient sentence that front-loads the core action and benefit ('Flush WordPress rewrite rules (fixes permalink issues)'). Every word adds value without redundancy, making it highly concise and well-structured.

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 the tool has 0 parameters and no output schema, the description is minimally adequate by explaining what the tool does. However, for a tool that likely involves system-level changes (rewrite rules), it lacks details on behavioral context, side effects, or usage scenarios, which are important for safe invocation.

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 parameters with 100% coverage, so no parameter documentation is needed. The description appropriately avoids discussing parameters, focusing instead on the tool's purpose and effect, which aligns with the schema's simplicity.

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 clearly states the action ('flush') and resource ('WordPress rewrite rules'), with a specific purpose ('fixes permalink issues'). It distinguishes from siblings by focusing on a maintenance operation, though it doesn't explicitly contrast with similar tools like 'wordpress_clear_cache'.

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 implies usage when there are 'permalink issues,' but provides no explicit guidance on when to use this tool versus alternatives, prerequisites, or warnings. It lacks context about when this operation is necessary or safe.

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