Create WP Credentials

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

Annotations only cover the generic safety profile; the description adds the operationally critical facts: the password is returned once and must be saved, the default is a least-privilege porkbun-agent/editor user, administrator implies arbitrary code execution and requires acknowledge_full_access, and there is a 20-per-hour rate limit.

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?

Front-loaded with the CLOUD FOR WORDPRESS ONLY scope and the core action, then the caveats. Dense but every sentence carries a distinct constraint; only the restated 'save it immediately' warning is mildly redundant with the one-time-return statement.

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?

No output schema exists, and the description covers what matters about the return value (one-time password, save immediately) plus the credential semantics. For a 5-param mutation with full schema coverage and annotations, nothing material is missing.

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 coverage is 100%, so the baseline would be 3, but the description reinforces the role/acknowledge_full_access coupling with consequences the schema cannot encode (full site control, code execution). It adds risk semantics beyond the enum labels rather than merely restating them.

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?

States a specific verb (mint), resource (WordPress Application Password for a domain's managed WP site), and the downstream purpose (drive it over the WP REST API with Basic auth). An agent can distinguish this instantly from list_wp_credentials, delete_wp_credentials, and deploy_site.

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?

Explicit prerequisites (site provisioned and ACTIVE, poll get_hosting), explicit exclusion (free $0 preview sites), explicit routing to a sibling for cleanup (delete_wp_credentials), and an escalation condition for the administrator role. Nothing is left to inference.

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