wordpress_flush_rewrite_rules

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

No annotations are provided, so the description should disclose behavioral traits such as side effects, permission requirements, or state changes. The description only states the action and an implied benefit; it does not mention that flushing rewrite rules modifies WordPress state, may be a heavier operation, or could briefly affect the site. This leaves the agent without important context about consequences.

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 short sentence that front-loads the action ('Flush') and the target resource. Every word earns its place, and there is no unnecessary detail. It is concise while still conveying purpose and use case.

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's simplicity (no parameters, no output schema, single action), the description is largely complete. It explains what it does and why. However, a mention of potential side effects or prerequisites (like needing admin access) would make it fully complete, but this is not critical for such a straightforward tool.

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 tool has zero parameters, so the baseline is 4 per the rubric. The description adds no parameter information because none exists; the empty schema is sufficient. No further semantic guidance is needed.

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 uses a specific verb ('Flush') and resource ('WordPress rewrite rules'), and adds the purpose ('fixes permalink issues'). This clearly distinguishes it from all sibling tools, which focus on posts, media, users, etc. The action is unambiguous.

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 phrase 'fixes permalink issues' tells the agent when to use this tool. There are no explicit alternatives or exclusions, but given that no sibling tool performs a similar function, the usage context is clear. It could benefit from saying when not to use (e.g., if permalinks are not the issue), but this is a minor gap.

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