wordpress_rest_request

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

With no annotations, the description carries full burden for behavioral disclosure. It mentions write guards for non-GET requests but does not explain what 'write guards' entail, what happens if blocked, or any authentication, rate-limiting, or safety implications. As a powerful tool, this is insufficient.

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 extremely concise: two sentences with no redundant words. It front-loads the core purpose and adds a key behavioral note. Every word 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 the complexity (generic escape hatch, 4 parameters including a nested object, no output schema, no annotations), the description is far too brief. It lacks explanation of return values, error handling, usage patterns, and prerequisites, leaving agents underinformed 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?

Schema description coverage is 0%, so the description must compensate. It only references the method parameter implicitly via 'Non-GET requests' and does not explain path, body (a nested object), or confirmDelete parameters. No guidance on how to construct the body or select valid paths.

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 it's an 'Advanced escape hatch for WordPress REST API calls', specifying the action (making API calls) and the resource (WordPress REST API). It conveys the tool's role as a generic endpoint caller, but does not explicitly distinguish it from sibling tools that cover specific endpoints, leaving some ambiguity.

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 hints at usage context by noting 'Non-GET requests obey write guards', but does not explicitly state when to use this tool versus the specific sibling tools (e.g., wordpress_create_post). It lacks guidance on when not to use it (e.g., for standard CRUD operations) or what alternatives exist.

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