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

Annotations already declare read-only/idempotent/no-destruction; the description reinforces this and adds 'runs straight away', which usefully signals no approval step. It also discloses result-shape behaviors (content_length for size triage, snippet returns slug and snippet fields) that go beyond the annotations.

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?

Front-loads the core action, then layers the snippet tip, result fields, and the safety note. Four short sentences with no real filler; only the parenthetical site note is marginal.

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, the description usefully names returned fields (content_length, snippet, slug) and explains excerpt behavior, which is enough for correct invocation. The main gap is the undocumented post_type parameter and the unstated scope of 'all content'.

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 67% and the description adds genuine meaning for `snippet` (excerpt around match, token savings, fields returned). However, status, per_page, and especially the undocumented `post_type` parameter get no added semantics, so the description only partially compensates.

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 and resource ('Search all content') and implies the difference from fetching tools by noting snippet savings vs. wp_get_page. 'All content' is slightly vague about whether media/comments/terms are included, and it doesn't name the closest list siblings (wp_get_pages, wp_search_posts) directly.

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?

Gives a clear use condition: set snippet>0 to get excerpts and save tokens instead of fetching each result with wp_get_page. That is a real when-to-use cue, but it offers no explicit exclusions for when to prefer wp_get_pages or the other search variants.

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