Three tools with complete input/output schemas and descriptions. Naming follows verb_noun pattern (list-ads, get-ad, create-ad). Descriptions are adequate (40-60 chars) but lack actionable context for LLM selection. Parameters have types and descriptions, but lack enums for constrained values (e.g., status should be enum, not free-form string). Output schemas documented but sparse. Error handling present but minimal, no recovery guidance. Tool annotations auto-generated via filter function (readonly, destructive, idempotent) which is good, but not exposed in tool metadata for MCP clients. No pagination guidance in list-ads despite accepting limit/offset.

• Convert status parameter to enum: {"type": "string", "enum": ["publish", "draft", "pending", "private", "future", "any"], "default": "any"}. Remove the free-form string and validation logic from the callback.
• Expand tool descriptions to 100-150 chars. Example: 'List all Advanced Ads advertisements with optional filtering by status. Returns paginated results (max 200 per page). Use this to discover available ads before calling get-ad for details.'
• Add recovery guidance to error responses. Example: 'Ad not found (ID: 123). Try calling advads/list-ads to see available ad IDs, or check if the ad was deleted.'
• Define a schema for the 'options' object in create-ad. Document which keys are valid (e.g., placement_id, expiry_date, conditions). If options are dynamic, provide an example or link to Advanced Ads documentation.
• Expose tool annotations in MCP tool metadata. Add 'annotations' field to wp_register_ability output so MCP clients can read readonly/destructive/idempotent hints without parsing WordPress internals.