List recent blog posts

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

The annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds meaningful behavioral context: the feed only contains the newest posts, the blog covers both Capacitor and Ionic Framework, and each returned post includes specific fields. This goes beyond bare annotation coverage without contradicting it.

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?

The description is concise yet information-dense. Each sentence serves a purpose: defining scope, giving usage guidance, describing output fields, and providing a clear exclusion with an alternative. Key facts are 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?

For a simple zero-parameter read-only tool, the description is complete: it specifies source, ordering, recency limit, return fields, applicable use cases, and the correct sibling tool for documentation questions. No important context is missing.

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?

The tool has zero parameters, so the schema carries no parameter documentation burden. The baseline for 0-parameter tools is 4, and the description appropriately focuses on output and usage rather than parameter details that do not exist.

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 clearly states the tool's function: listing the 10 most recent posts from the Capacitor tag of the Ionic blog, newest first. It names a specific resource and scope, and the presence of sibling tools like search_docs and get_doc_page makes the boundary between them easy to infer.

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?

The description explicitly states when to use this tool ('when the question is about what is new — recent releases, announcements or deprecations') and when not to use it ('Do not use this to answer a documentation question'). It also names the alternative, search_docs, making the routing decision unambiguous.

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