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

Annotations already establish readOnly/idempotent/non-destructive and closed-world, so the safety profile is covered. The description adds genuinely useful behavioral context beyond that: results are metadata-only (id, title, kind, author, date) and content requires a follow-up call. Paging behavior itself is left to the schema, keeping it just 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?

Four tight sentences, front-loaded with the resource and scope, then the source/query routing, then the return shape and the get_blog_post handoff. The first sentence is long and list-heavy but every clause distinguishes a real content category rather than padding.

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 explicitly and stating that payloads are metadata only, so an agent knows to follow up with get_blog_post for text. Combined with the exclusion of release notes and the All-tab default, nothing needed to call this 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 coverage is 100%, so baseline is 3, but the description adds cross-parameter meaning the schema only implies: omitting source yields 'All', which is first-party writing only, and query matches titles and text. The limit/offset paging parameters get no mention in the description, which is the only reason this isn't higher.

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?

Specific verb+resource ('List the blog posts CCPEDIA holds') followed by an enumeration of exactly what the corpus contains (articles, news, press releases, partner press, network notices, third-party reprints). It also explicitly separates release notes from blog posts, which is the most likely confusion source given the sibling search_release_notes tool.

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 routing rules: omit source for the All view, pass query to search, and call get_blog_post with an id when full content is needed. It also excludes a related-but-wrong path by saying release notes live under /releases, naming the alternative rather than leaving the agent to guess.

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