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

The annotations already establish that the tool is read-only, open-world and idempotent, so the safety profile is covered. The description adds behavior the annotations do not: results are aggregated across several source categories, ordered newest first, and carry source, date, summary and link. It doesn't mention result volume limits or how the source mix is chosen, which is why this is not a 5.

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?

It opens with the trigger condition, then supplies the resource and return shape, then routes the agent to the alternative tool. That is well front-loaded with no filler. The single long middle clause is dense but each part carries information the agent needs.

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?

There is no output schema, and the description usefully describes what comes back: source, date, summary and link, in newest-first order. The only meaningful gap is that it never explains how `kind` and `limit` shape the result set. For a two-parameter read-only news tool, that is a minor omission rather than a blocker.

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 only 50%: `kind` has a short description and `limit` has none. The description compensates by naming the source categories the user can target ('official WordPress blogs, news sites, security researchers and makers'), which maps onto the `kind` enum values. It still doesn't explain that only one kind may be selected per call, or what `limit` does and how it is bounded.

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?

The description names a specific verb and resource: 'the latest articles from official WordPress blogs, news sites, security researchers and makers, newest first'. It also lists the exact fields returned (source, date, summary, link), so the agent knows what it gets without opening a schema. It explicitly sets itself apart from wp_now, which covers 'what changed and what to do in code'.

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 gives a clear trigger ('Use when the user asks what is new in WordPress, or a recent release or announcement may matter to the task') and a clear exclusion that names the alternative: 'For what changed and what to do in code, use wp_now.' This is explicit when-to-use and when-to-use-something-else guidance, with nothing left to inference.

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