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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the safety profile is covered. The description adds genuinely useful scoping: what is removed is the connection plus the stored key reference, not the WordPress site's content — an important distinction given the tool name says 'delete site'. It omits reversibility and the behavior on a second call despite idempotentHint=false.

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?

A single sentence with zero filler, front-loading the primary action (disconnect) before the secondary effect (key reference deletion). Nothing is padded or repeated.

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?

For a one-parameter teardown tool with rich annotations and no output schema, the description covers the essential question of what is destroyed. Minor gaps remain around idempotency/reversibility and how to re-establish the connection, but nothing critical 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?

Only one parameter (site_id) and schema description coverage is 100%, so the schema fully documents it. The description adds no format hints or meaning beyond the schema, so the baseline of 3 applies.

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 pair and resource: 'Disconnect a WordPress site from Xyle and delete its stored key reference.' This clearly sets it apart from connect_wordpress, verify_wordpress, set_wordpress_connection, and get_wordpress_site. It does not explicitly name a sibling, but the action is distinctive enough that an agent can place it.

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?

No indication of when to use this versus alternatives (revoke_api_key, set_wordpress_connection, or simply leaving the connection in place), and no prerequisites or exclusions. The agent must infer that this is the teardown counterpart of connect_wordpress.

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