hosting_deleteWordPressInstallationV1

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

No annotations provided. Description mentions 'optional file and database removal' but input schema lacks any parameter to control this option, creating ambiguity. It does clarify that all associated data is removed, but behavioral inconsistency lowers score.

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?

Two sentences: first states purpose and scope, second provides key usage hint. No redundancy; all information 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?

Covers deletion scope and identifier source, but lacks return value details and error conditions. No output schema, so description should indicate what to expect (e.g., success confirmation).

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 covers 100% of parameters. Description adds value by explaining the 'software' parameter is an identifier and how to obtain it, but the 'username' parameter remains generic ('username parameter') with no additional context.

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 deletes a WordPress installation and lists removed components (plugins, themes, staging). It distinguishes from sibling tools like 'uninstallWordPressPlugins' by mentioning full removal, but lacks explicit contrast.

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?

Provides guidance on obtaining the installation identifier via GET endpoint, but no direction on when to use this vs alternatives, prerequisites, or handling dependencies.

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