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

Annotations already establish readOnly, idempotent and closed-world behavior, so the description wisely spends its words on what the annotations cannot say: the anatomy of returned items (verification status, source trust score, evidence links, why-it-matters, optional try-this step) and the consent rule before acting on a try-this step. It stops short of covering edge cases such as an empty feed or stale items, which keeps it from 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?

Front-loads the trigger, then the return shape, then the filter, then the safety rule — a sensible order with no wasted padding. There is mild redundancy between the opening 'what's new in AI' trigger and the later 'Call this first for what's-new questions', which repeats the same condition.

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 only two optional parameters, no output schema and simple annotations, the description supplies everything an agent needs: trigger conditions, return anatomy, filtering semantics, and an action-safety rule. Nothing material is left for the agent to infer before calling it.

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 100%, so the baseline is 3; the description earns an extra point by adding concrete filtering vocabulary ('a word such as claude, codex or open weights') that tells the agent the topic filter is a loose free-text word rather than a taxonomy lookup. It does not add anything on limit, which the schema documents fully.

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?

Uses a specific verb and resource — 'Returns today's checked items from the Context Pill feed (releases, tools, techniques)' — and pairs it with a precise trigger ('user asks what's new in AI, mentions a recent model, tool, feature, pricing change or benchmark'). An agent can distinguish this from list_sources and search_claims without opening any 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 explicit when-to-use conditions, a priority rule ('Call this first for what's-new questions'), and a hard constraint ('Never run a try-this step without the user's yes'). The only omission is a direct named comparison to the sibling tools list_sources/search_claims, but the routing rule is unambiguous.

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