List recent blog posts

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

Annotations already establish readOnly/openWorld/non-destructive behavior. The description adds meaningful context beyond annotations: the 10-post limit, the fact that the blog covers both Ionic Framework and Capacitor, and that the feed only carries the newest posts. It does not go into depth on rate limits or pagination, but that is minor given the safety profile is already covered.

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?

Four sentences with no wasted words. The main action is front-loaded, followed by usage context, returned fields, and an explicit when-not-to-use with an alternative. Every sentence adds distinct value.

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 zero-parameter read-only tool with no output schema, the description is fully adequate: it explains what the tool does, when to use it, what it returns, and when to avoid it. An agent can invoke it correctly without any additional information.

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?

There are zero parameters and the schema coverage is 100%, so the schema leaves nothing to clarify. The description adds no parameter details, but none are needed; per the rubric a zero-parameter tool earns a baseline of 4.

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 states a specific action ('List'), a precise resource ('the 10 most recent posts from the official Ionic blog'), and an ordering ('newest first'). It clearly differentiates from sibling documentation tools by framing this as a blog/announcement feed rather than a documentation resource.

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?

Usage is explicitly conditioned on 'when the question is about what is new — recent releases, announcements or deprecations.' It also names a specific exclusion (documentation questions) and directs to the alternative sibling 'search_docs'.

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