List recent blog articles

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

No annotations are present, so the description carries the burden. It discloses ordering (newest-first) and the result cap (up to 50), and because there is no output schema it usefully describes the return shape. It does not address permissions, pagination beyond the cap, or what happens when no articles match, which keeps it short of 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?

The description is front-loaded with the core verb and payload, and the follow-up get_article call is placed before the less important cap details. It is slightly redundant in restating the limit/ordering facts already in the schema, but there is no filler sentence.

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 single-optional-parameter list tool with no output schema, the description supplies everything an agent needs: the fields returned, the ordering, the cap, and the natural follow-up tool. Nothing required to call it correctly 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?

Schema description coverage is 100% and the single limit parameter is already documented there, including default 10, max 50, and newest-first ordering. The description repeats that same information ('Returns newest-first, up to 50 (default 10)') without adding syntax or behavior beyond the schema, so the baseline of 3 applies.

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 ('List the most recent posts from the Refined Element blog') and enumerates exactly what each item contains: title, publish date, one-line summary, and slug. It also distinguishes itself from the sibling get_article, which returns the full text rather than the index.

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 an explicit when-to-use ('Use this to see what Refined Element has published on Xperience by Kentico, GEO, AI-driven development, and agent commerce') and names the alternative/next step with its argument shape ('then call get_article(slug) for the complete text'). The routing decision between the two tools is fully stated.

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