save_wordpress_credentials

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

With no annotations, the description carries the full burden. It discloses that the tool validates the connection before saving, which is a key behavioral trait. However, it fails to mention side effects like overwriting existing credentials, failure behavior, or required permissions. The disclosure is partial but not misleading.

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 concise sentence that is front-loaded with the action. It avoids redundancy and every word adds value. It is appropriately sized for a simple tool, though it could be slightly more explicit without losing conciseness.

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 no annotations and no output schema, the description is underspecified. It omits critical context such as what happens on failed validation, whether existing credentials are replaced, and what the response looks like. The validation hint is useful, but for a mutation tool with four required parameters, the description is not complete enough for an agent to invoke it safely.

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 provides 100% description coverage for all parameters, so the baseline is 3. The description adds minimal semantic context beyond the schema—only that this connects WordPress to a site, which loosely binds site_id, wp_url, and credentials. It does not elaborate on parameter formats or relationships, but schema already covers the basics.

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: 'Connect WordPress to a site', which is a specific verb plus resource. The added 'validates connection first' gives useful context. However, it does not explicitly distinguish from sibling tools like 'delete_wordpress_credentials' or 'get_wordpress_status', though the connection intent is clear.

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?

There is no explicit guidance on when to use this tool versus alternatives. The mention of 'validates connection first' implies a prerequisite (valid credentials) but does not state scenarios such as initial setup or updating credentials. No exclusions or alternative tool references are provided.

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