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

Annotations already declare destructiveHint=true and non-idempotent, so the safety profile is covered; the description adds real value by disclosing the latency ('slow; waits'), the per-target result shape, and the confirmToken gating mechanism that explains how the destructive action is controlled. It doesn't say what happens to an existing page at a colliding slug or what authorization is needed.

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?

Three tight sentences, each earning its place: the sibling comparison, the latency/return behavior, and the destructive two-phase flow. The most consequential information (live publication + confirmation) is front-loaded.

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 12-parameter destructive tool with no output schema, the description covers purpose, alternative, latency, return granularity, and the confirmation protocol well. Remaining gaps — slug-collision behavior, per-target failure handling, and rate limits — are secondary but non-trivial for a publish action.

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 58%, so the schema documents roughly half the parameters (site, targets, baseKeyword, etc.). The description adds usage meaning for confirmToken (omit on first call to get a summary and token), which is useful, but says nothing about targets, templatePageId, templatePurpose, or the other 9 parameters.

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?

Names a specific verb+resource (publish location pages) and anchors it against the sibling generate_location_page_drafts, making the key distinction — pages go live on WordPress immediately — explicit. An agent can separate this from the draft-generating sibling without opening either schema.

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 comparison to generate_location_page_drafts implicitly routes the agent: use that tool for drafts, this one for live pages. It also spells out the two-phase confirmation workflow. It stops short of an explicit 'when not to use' (e.g. don't call without reviewing the first-call summary).

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