wordpress_test_connection

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

With no annotations, the description carries the full burden of disclosure. It mentions that it verifies credentials and returns connection status, which adds context beyond the name. However, it lacks details on error behavior, side effects, or the exact structure of the response (though an output schema exists). It is adequate but not rich.

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 two concise sentences, front-loaded with the primary action. Every word serves a purpose, with no redundancy or filler. It is well-structured and easy to parse.

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?

The tool is simple (no parameters, has an output schema), and the description sufficiently conveys its function. It lacks explicit guidance on failure handling or prerequisites, but given the tool's minimal nature, the description is complete enough for an agent to use it correctly.

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 and schema coverage is 100% (vacuously). Per the guideline, a baseline of 4 is appropriate. The description adds no parameter-specific information because none are 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 clearly states the tool's purpose: 'Test connection to WordPress REST API' and 'Verifies API credentials and returns connection status.' This is a specific verb-resource pair (test connection, verify credentials) that distinguishes it from sibling tools focused on CRUD operations for posts, pages, media, etc.

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 provides clear context for when to use this tool (to test connectivity and credentials) but does not explicitly state when not to use it or compare it to alternatives. However, the intent is unambiguous and the tool's unique role among the siblings is obvious, so no exclusions are needed.

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