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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so 'Read only' is redundant. Value beyond annotations comes from 'Searchable and paginated' and the enumerated return fields (id, title, slug, link, status), which matter since there is no output schema.

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 short sentences: purpose and return fields first, then capability, then platform constraint and safety. Zero filler and well 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?

With no output schema, listing the returned fields and mentioning pagination covers most of what an agent needs. The only real omission is pagination defaults/page-size behavior for the four parameters.

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 description coverage is only 25% (just 'site'), so page, search and perPage are undocumented. 'Searchable and paginated' loosely maps to search and page/perPage, but no format, defaults, or max (perPage max 100) are given, so it only partly compensates for the gap.

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 resource ('the site's existing WordPress pages') and its role ('that generate_location_page_drafts can clone'), which no other sibling list_* tool covers. An agent can distinguish it from list_articles/list_photos/list_sites immediately, and the returned fields are named.

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?

It ties the tool to a concrete workflow by naming the downstream consumer generate_location_page_drafts, and gives a platform constraint ('WordPress sites only'). It stops short of explicit when-not guidance or naming an alternative (e.g., fetch_sitemap_links) for non-WordPress sites.

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