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

Annotations only declare readOnlyHint=true, so the description usefully adds behavioral context the annotation lacks: results are ordered newest first and include date, category, summary and URL. It does not mention pagination behavior or that lang selects the underlying site edition beyond what the schema says, but the added context is substantive.

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?

Two sentences, zero waste. What the tool returns and how it is ordered comes first, and the routing hint to search_site is placed last as a contrast.

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 compensates by naming the returned fields and ordering, and it covers filtering and the sibling alternative. Only minor gaps remain (no pagination or rate-limit note), so it is complete enough to call correctly.

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%, so all four parameters (lang, limit, since, category) are already documented in the schema, including enums and defaults. The description restates filtering by category/date without adding syntax or format detail beyond the schema; baseline 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 Codemate's published articles') plus ordering ('newest first') and the fields returned (date, category, summary, URL). An agent can distinguish this from the sibling list_* tools and search_site without opening the schema.

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 use case ('what Codemate has written or published about something, or for recent news') and names the competing alternative with the discriminating condition: search_site only returns the closest few matches. That is a clear when-to-use plus when-to-prefer-another.

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